doctor & upgrade

alfe doctor

alfe doctor diagnoses the health of your setup. Run it whenever something seems off — it’s the fastest way to see whether the CLI is configured, your credentials are valid, and the agent daemon is connected.

alfe doctor

It checks:

• Configuration. That ~/.alfe/config.toml exists and is readable.
• Authentication. That your API key is valid.
• Gateway daemon. That the local daemon is running and connected to the Alfe cloud, and reports a health summary.

Use it right after alfe setup to confirm everything came up, and any time an agent appears offline.

Keeping the CLI up to date

The CLI is distributed on npm as @alfe.ai/cli. Upgrade it the same way you’d upgrade 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

Check the installed version at any time:

alfe --version

Note

There is no alfe upgrade subcommand — updating the CLI is a standard npm install. After upgrading, you can re-run alfe setup (it’s safe to re-run) to pick up any new configuration.

Keeping a managed agent up to date

For agents running on Alfe-managed hosts, updates are handled for you — you can manage them from the dashboard at app.alfe.ai rather than running upgrade commands on the machine yourself.