Skip to main content

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 exact sections depend on the installed version and configured features. They can include:

  • active Profile, default Role, home, config, state, and workspace paths;
  • Gateway listener and live RPC reachability;
  • configured provider/model and credential-reference state;
  • channels, cron, heartbeat, MCP, and storage status; and
  • runtime/version mismatch warnings.

Always confirm the Profile and paths at the top before interpreting a later failure.

What Doctor Checks​

Doctor probes the filesystem, configuration, provider setup, Gateway listener posture, and enabled subsystems. Each finding has a status and safe detail; actionable findings include remediation instead of exposing secrets.

Start broad, then go specific

Run anyy doctor first. Use a feature-specific doctor only after the broad result points there, such as anyy browser doctor or 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​

FindingAction
Gateway unreachableCheck anyy gateway status, then start or restart it
Credential reference unresolvedReplace the key from Models, Tools, or Channels
Listener posture warningUse the recommended local bind or secure the remote path
Channel degradedOpen Dashboard → Channels and run anyy channel doctor CHANNEL
Storage pressureCreate a backup, inspect Profile storage, then use supported maintenance
Version mismatchComplete the update and restart the installed Gateway service

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