Claude Code Auto Mode: A Classifier Instead of an Allowlist

The Stack

Steps

1. 1

   Set Auto Mode as your default

   Set it in ~/.claude/settings.json (it is ignored in project settings on purpose), or cycle to it with Shift+Tab. A separate classifier model reviews each action before it runs and blocks anything that escalates beyond your request.

   cat > settings.json <<'EOF'
   {
     "permissions": {
       "defaultMode": "auto"
     }
   }
   EOF
   echo "wrote ~/.claude/settings.json (defaultMode: auto)"

2. 2

   What CI checks: the settings block is valid and the requirements are surfaced

   CI confirms the settings JSON is valid with defaultMode auto, and surfaces the documented availability requirements as a checklist (corrected against code.claude.com/docs). The classifier-gated run needs a live model and account, so that part is fenced.

   cat > checkauto.mjs <<'EOF'
   import { readFileSync } from 'node:fs';
   const cfg = JSON.parse(readFileSync('settings.json','utf8'));
   const p = cfg.permissions || {};
   let ok = true;
   function check(label, cond){ console.log(label + ': ' + (cond ? 'yes' : 'NO')); if(!cond) ok=false; }
   check('settings valid: defaultMode auto', p.defaultMode === 'auto');
   if(!ok){ console.log('auto mode config check FAILED'); process.exit(1); }
   console.log('Auto Mode requirements (code.claude.com/docs):');
   console.log('  - Claude Code v2.1.83 or later');
   console.log('  - Available on all plans');
   console.log('  - Anthropic API: Opus 4.6 or later, or Sonnet 4.6');
   console.log('  - Bedrock/Vertex/Foundry: Opus 4.7 or 4.8 with CLAUDE_CODE_ENABLE_AUTO_MODE=1');
   console.log('  - Team/Enterprise: an admin must enable it first');
   console.log('  - defaultMode auto honored only in ~/.claude, ignored in project settings');
   console.log('auto mode config check OK');
   EOF
   node checkauto.mjs

3. 3

   Let it run (the classifier + model step, not checked by CI)

   In Auto Mode the classifier and the agent both invoke models, which are non-deterministic and account-gated. CI verifies the config and the requirements checklist, never the live run.