faelo-doctor

Faelo doctor — connectivity preflight

Run this when Faelo isn't responding or the user just set up the plugin.

Checks (in order)

1. Tools present? Are the mcp__faelo__* tools available in this session? NO mcp__faelo__ tools at all means one of two things:

   • (a) The plugin/session isn't loaded — run /plugin, confirm faelo is installed + enabled, then start a new Claude Code session (MCP connects at session start).
   • (b) The key is missing or invalid — the remote server gates EVERY request on the Authorization: Bearer token, so a bad key makes the whole MCP connection fail and NO tools appear (there is no auth-free endpoint). Re-enter the key (step 2), restart.

2. Connected + which account? Call mcp__faelo__whoami — the single connectivity + identity probe. (mcp__faelo__ping only confirms reachability and, with auth on, also needs a valid key — so it is NOT an auth-free liveness check.)

   • whoami errors / connection fails → key invalid or server unreachable. Re-enter the key: run /plugin, disable then re-enable faelo (Claude Code re-prompts for the Faelo API Key) — or uninstall and /plugin install faelo. Paste your fae-<label>-<hex> key, then start a new session. There is no /plugin config command. Keys are issued by the Faelo team — if you don't have one, request it.
   • whoami ok → connected. Report the account: label, credit balance, project count. If balance is 0, project creation will fail — they need credits.

3. Ready to build? If whoami succeeds and balance > 0, hand off to faelo-orchestrate (make an ad) or faelo-ship (one-shot from a config).

What you CANNOT fix from here

• Issuing a key (Faelo team only).
• Granting credits (Faelo team / billing).
• Server downtime (escalate to the Faelo team).

Report findings as a short checklist (✅/❌ per check) + the single next action.