Troubleshooting
Fix common AutoMode problems: nothing changes after install, the mod is not listed, the bar is idle or missing, a hook is skipped, and filing a bug.
| Symptom | Check |
|---|---|
| Nothing changes after install | Run /reload-plugins. Then run /plugin and look for 1 mod active · automode. |
| The mod is not listed | Check claude --version is 2.1.287 or later. Run claude plugin test in a folder that holds no mod: the message says whether mods can load. |
| The bar says AutoMode is idle | You set "activation": "picker" and the model ID does not match. Use "always", or run /automode setup. |
| The bar is missing in VS Code | Expected. Claude Code does not draw the band there. Use /automode. |
| Routing only records, never switches | You are on Vertex, Bedrock, Foundry or a gateway. See Where AutoMode runs. |
/automode says the mod is not loaded | Restart Claude Code. |
| A hook seems skipped | Start with claude --debug and search the log for automode. See Troubleshoot a mod. On a managed machine, see Organizations. |
| Plan mode or compaction acts odd at work | Managed settings skip some hooks. See Organizations. |
File a bug
Run the debug report
/automode debug prints a report to paste. It holds no prompt text, and it masks your home folder.
Open an issue
Open an issue. Say what the bar showed and what you expected, and paste the report.
Last updated on
AutoMode compared with other routers
AutoMode against effortless, jev-router and claude-router for Claude Code: features, how each runs, measured cost on the same sessions, and trade-offs.
FAQ
Answers about AutoMode for Claude Code: cost, plans and API keys, quality, the prompt cache, privacy, VS Code, and how it differs from auto mode.