Skip to Content
AutoMode

Environment variables

AutoMode environment variables: turn off the router, bar or guardian, force a policy, override the thinking guard, and the provider variables it reads.

Environment switches apply last, so they win over config.json and plugin settings.

VariableValuesEffect
AUTOMODE_ROUTERoffTurn routing off everywhere.
AUTOMODE_POLICYauto, legacyForce the routing policy.
AUTOMODE_UIoffHide the bar. Routing goes on.
AUTOMODE_GUARDIANoff, observe, recommend, assist, autoSet the guardian mode. off leaves the rest of AutoMode running.
AUTOMODE_GUARDIAN_CONFIGA JSON objectGuardian keys over config.json, for a test profile or one machine. Unknown keys are ignored.
AUTOMODE_SIGNALSoffStop reading the signals file that stands in for hooks Claude Code skips under managed settings.
AUTOMODE_THINKING_GUARDon, offOverride the guard that leaves effort alone where a thinking setting could make the API refuse an effort change.

Variables AutoMode reads but never sets

VariableWhy
CLAUDE_CODE_USE_VERTEX, CLAUDE_CODE_USE_BEDROCK, CLAUDE_CODE_USE_FOUNDRY, ANTHROPIC_BASE_URLTo tell the provider. Off the Anthropic API, the router runs in shadow.
CLAUDE_CODE_DISABLE_EXPERIMENTAL_BETASWith it set, an effort change may not keep the cache, so effort is priced like a switch.
MAX_THINKING_TOKENS0 turns the thinking guard on.
ANTHROPIC_API_KEYOnly to test whether it is set, so AutoMode can tell a plan from an API key. It never stores or sends the value.
HOMETo find the data folder.

AutoMode never calls $.env.set. See Review it before you install it.

Last updated on

On this page