doctor & upgrade

Run alfe doctor whenever an agent seems off. It’s the fastest way to see whether the CLI is configured, your key is valid, the daemon is connected, and the runtime is ready. This page also covers how to update the CLI.

Run alfe doctor

Terminal

alfe doctor

It runs these checks and only reports. It doesn’t change anything:

• Configuration — ~/.alfe/config.toml exists and is readable.
• API key — your key is valid.
• Gateway daemon — the daemon is reachable, with a health summary.
• Runtime — extra checks for some terminal runtimes.

Runtime checks

Doctor picks these from the agent’s runtime:

Runtime	What doctor checks
Claude Code (self-hosted)	claude is on your PATH, how it’s signed in, and whether ANTHROPIC_API_KEY is set in your environment.
Codex, Gemini CLI, Grok Build	The Alfe host is installed, the provider CLI is at the version Alfe pinned, and the local login state.

If doctor reports a missing host, re-run alfe setup.

Note

An ANTHROPIC_API_KEY in your shell forces Claude Code to bill that API key instead of your subscription login. Doctor flags it so you can unset it.

Update the CLI

The CLI is distributed on npm as @alfe.ai/cli. Update it the same way as any global npm package:

npm

npm i @alfe.ai/cli@latest -- -g

pnpm

pnpm add @alfe.ai/cli@latest -g

bun

bun add @alfe.ai/cli@latest -g

Then check the installed version:

Terminal

alfe --version

Note

There’s no alfe upgrade subcommand. After updating, you can re-run alfe setup to pick up new configuration.

Update a managed agent

Alfe updates the CLI on managed machines. When a newer version is available, you can also start the update yourself: select Upgrade on the agent’s status section in the dashboard, then choose a version. The agent restarts during the upgrade.