Skip to main content
Quick answers plus deeper troubleshooting for real-world setups (local dev, VPS, multi-agent, OAuth/API keys, model failover). For runtime diagnostics, see Troubleshooting. For the full config reference, see Configuration. This page is an index. The day-to-day FAQ is split across thirteen pages, one per topic. The triage ladder stays on this page; open the page that matches your question.

​
First 60 seconds if something is broken

1

Quick status

Fast local summary: OS + update, Gateway/service reachability, agents/sessions, provider config + runtime issues (when the Gateway is reachable).
2

Pasteable report (safe to share)

Read-only diagnosis with a log tail (tokens redacted).
3

Daemon + port state

Shows supervisor runtime vs RPC reachability, the probe target URL, and which config the service likely used.
4

Deep probes

Live Gateway health probe, including channel probes when supported (requires a reachable Gateway). See Health.
5

Tail the latest log

If RPC is down, fall back to:
File logs are separate from service logs; see Logging and Troubleshooting.
6

Run the doctor (repairs)

Repairs/migrates config and state, then runs health checks. See Doctor.
7

Gateway snapshot (WS-only)

Asks the running Gateway for a full snapshot. See Health.

​
Quick start and first-run setup

First-run Q&A - install, onboard, auth routes, subscriptions, initial failures - lives on the First-run FAQ.

​
Models, failover, and auth profiles

Model Q&A - defaults, selection, aliases, switching, failover, auth profiles - lives on the Models FAQ.

​
Miscellaneous

Credentials and model selection are separate. Setting ANTHROPIC_API_KEY (or storing an Anthropic API key in auth profiles) enables authentication, but the actual default model is whatever you configure in agents.defaults.model.primary (for example anthropic/claude-sonnet-4-6 or anthropic/claude-opus-4-6). No credentials found for profile "anthropic:default" means the Gateway could not find Anthropic credentials in the SQLite auth stores available to the running agent.
Still stuck? Ask in Discord or use the GitHub issue chooser.

​
Where each section moved

Every question heading from the previous single-page version keeps its anchor here, so an existing link such as /help/faq#where-things-live-on-disk still resolves. Each entry points at the page that now holds the answer.