Status & Doctor

status describes what Anyy is using. doctor checks whether that configuration and its dependencies are healthy. Both are read-only diagnostic commands.

Quick Check

anyy status
anyy doctor

Use structured output for automation or support collection:

anyy status --json
anyy doctor --json

status can inspect an offline Profile without creating a missing state database. When the Gateway is reachable, it supplements local data with live runtime status.

What Status Shows

The command reports the selected Profile, default Role, Home, timezone and timezone source, Gateway state/listener posture, Cron, heartbeat, storage, MCP and Prompt Program status. When available, live Gateway values supplement the local snapshot.

Use anyy config for configuration paths, provider/model, endpoint and credential-reference details. status does not populate a full provider/model or Channel health report, and it is not a live model test.

Always confirm the Profile and paths at the top before interpreting a later failure. If CLI and Dashboard disagree, compare them with Dashboard → About; each may have selected a different Home or running binary.

What Doctor Checks

The CLI checks Home/Profile, configuration validity, timezone, Gateway listener posture, Cron, heartbeat, MCP and state storage. Findings use ok, warn, fail and info with details. Some MCP checks probe external connections. This command does not repair settings or certify a live model response; use Models and the matching Channel doctor for those checks.

Start broad, then go specific

Run anyy doctor first. Use a feature-specific doctor only after the broad result points there, such as anyy channel doctor CHANNEL.

Target Another Profile or Config

anyy --profile work status
anyy --profile work doctor
anyy doctor --config /path/to/config.yaml

Use an explicit config path only for diagnosis. It does not change the active Profile or install the file.

A Practical Recovery Order

1. Confirm Profile and paths with anyy status.
2. Read all failing and warning checks in anyy doctor.
3. Fix credentials or feature settings from their Dashboard page.
4. Run the matching feature doctor.
5. Restart the Gateway only if the remediation requires it.
6. Re-run both broad checks and save JSON output if the problem remains.

Common Findings

Finding	Action
Gateway unreachable	Check anyy gateway status, then start or restart it
MCP credential reference unresolved	Correct the referenced credential and rerun the MCP check
Listener posture warning	Use the recommended local bind or secure the remote path
A particular Channel is degraded	Open its detail page and run anyy channel doctor CHANNEL
Storage pressure	Create a backup, inspect Profile storage, then use supported maintenance
CLI and Dashboard use different builds	Compare About and anyy --version, then follow the update workflow

Diagnostics redact known secrets, but review files before sharing because user content and environment details may still be sensitive.