Doctor

Run doctor after installation and when an authenticated request fails unexpectedly:

loomloom doctor --output json

When credentials are present, the command checks the configured platform, public Market reachability, an authenticated executable-assets endpoint, and release information. A successful explicit check also registers and activates the verified Server profile. Useful JSON fields include:

Field	Meaning
`server`	Resolved base URL
`profile`	Saved name of the verified Server profile
`token_env`	Profile-specific environment variable generated by the CLI
`token_set`	Whether a token is configured; the token value is not printed
`token_valid`	Whether the selected credential passed authenticated verification
`platform`	Platform inferred or selected for the request
`platform_preset`	Whether the platform is a built-in ShengSuanYun or CogFoundry preset
`platform_operational`	Whether that platform is enabled for current flows
`healthy`	Whether the connectivity and authentication checks succeeded
`credential_action`	Setup action needed when credentials are incomplete
`credential_message`	Safe platform-specific recovery guidance
`next_action`	Whether to choose a Server, configure or persist a Token, or continue
`cli_version`	Installed CLI version
`release_channel`	Installed release channel
`update_available`	Whether a newer release was detected

Missing configuration can produce structured guidance with healthy: false without treating the diagnostic command itself as a process error. Inspect the returned fields; do not rely only on the shell exit status.

Verify and register a new Server

loomloom doctor \
  --server "<exact-server-url>" \
  --token "<matching-api-token>" \
  --name <optional-profile-name> \
  --output json

The Server is saved only after both public and authenticated probes succeed. If next_action is persist_token, write the Token under the returned token_env, then rerun loomloom doctor --output json. Do not persist a failed Server/Token pair.

When not to run doctor

For a local flag, file, JSON, workbook, or TemplateSpec validation error, fix the reported input first. Use doctor for authentication, endpoint, network, service-version, or unexpected server failures. Use --verbose only when needed:

loomloom doctor --output json --verbose

Verbose logs go to stderr. Review them before sharing and never add tokens or request payloads. See Troubleshooting for recovery paths.

loomloom CLI

TemplateSpec

loomloom API

loomloom API endpoints

Verify and register a new Server

When not to run doctor

​Verify and register a new Server

​When not to run doctor

Verify and register a new Server

When not to run doctor