Review it before you install it
Every mods API call AutoMode makes, and why: what it reads and writes, the four commands it runs, the calls it never makes, and how to check it yourself.
A Claude Code mod is code that runs with your permissions. It is not sandboxed. So the whole mod is open source: hooks/. Install mods only from authors you trust, and review them first.
List what it does without running it
git clone https://github.com/mralexivy/AutoMode
claude plugin validate ./AutoModeThe hooks: line lists the events AutoMode handles. The calls: line lists the mods API methods it uses. Checked on Claude Code 2.1.311:
| AutoMode calls | Why |
|---|---|
$.model.complete | One short Haiku call per prompt, for the judge. With delegation: on, one Haiku call for each extract, which sends the named files. It uses your own Claude login. |
$.fs.read, $.fs.write, $.fs.exists, $.fs.list | Reads config.json and your settings file. Writes its records, checkpoints and caches to its own data folder, ~/.claude/plugins/data/automode/. With debugLog on, it also writes a log in the plugin folder. |
$.process.run | Four commands. chmod and rm -f on its own data files. git rev-parse and git status, both read only, for the task checkpoint. |
$.env.get | Reads AUTOMODE_* switches, your provider variables, and HOME. It reads ANTHROPIC_API_KEY only to test whether it is set. It never stores or sends the value. |
$.store.get, $.store.set | Keeps small settings that Claude Code refused to keep. |
$.session.*, $.agent.*, $.prompt.*, $.tool.list, $.turn.abort, $.config.list, $.clock.* | Reads the session's model, usage and messages, and lists agents and tools. $.agent.spawn runs the six agents. $.prompt.compose and $.session.compact support handoff and compaction. $.turn.abort stops a turn when the guardian pauses it. |
$.ui.*, $.command.register | Draws the bar and adds /automode. |
What it never calls
AutoMode does not call $.http.fetch, $.mcp.*, $.env.set, $.prompt.submit or $.session.send. It has no network code of its own:
grep -rnE "fetch\(|https?://" hooks scripts workflowsThat finds only two comments that credit effortless. AutoMode sees every prompt and tool call, because it hooks prompt.submit and tool.call. That is how routing works. Nothing leaves your machine except through Claude Code.
What it writes
Only files in its own data folder, plus judge-log.jsonl in the plugin folder with debugLog on. It never edits a build, start-up, settings or instructions file.
Guards
- Subagents may not run git writes or
rm -rfwhile AutoMode is active. - The tool guards fail closed. If a guard throws before a call runs, the call is denied, Bash included.
- The
agent.spawnhook sets a subagent's model and effort. It does not change a permission mode.
Summary
- No key. It runs on your own Claude login.
- No server. There is nothing to host and no account to make.
- Your data stays local. See Privacy.
Last updated on
The Concise output style
AutoMode's optional Concise output style: short sentences, the answer first. Measured at 10% fewer output tokens, with code and quotes kept exact.
Privacy
AutoMode has no server, no account and no telemetry. Its judge calls go through your own Claude login. Every file it keeps, and how long it stays.