Claude Code’s Cheaper Auto Mode and the Proxy Trap

James Turner

Welcome to the lightning round, brought to you by Jellypod AI. Look, Anthropic just dropped Claude Code version 2.1.278, and if, if you run auto mode, your API bill is about to look a whole lot cleaner.

Lachlan Reed

Mate, it is, uh, about time. Every single background shell command or network check used to, to fire off a separate classifier request, and you paid full token price for every single one of those sanity checks.

James Turner

Right, but now, Anthropic shifted that safety classification right over to the server side at zero extra token cost. So when Claude Code checks an action before running it, those classifier tokens do not hit your bill anymore.

Lachlan Reed

Unless, of course, your corporate enterprise proxy decides to, to throw a spanner in the works.

James Turner

Oh man, the proxy trap! So here is what happens: if your network uses an LLM gateway that strips unrecognized payload fields, like safeguards or safeguard results, the server checks never reach your session.

Lachlan Reed

Exactly. Claude Code realizes it cannot talk to the server classifier, so it holds the prompt and hits you with that exact warning: We're changing auto mode to no longer charge for classifier requests in Claude Code. However, this session isn't eligible.

James Turner

And then it falls right back to client side checks, which means, well, you are back to paying for those classifier tokens.

Lachlan Reed

I actually got caught in this exact loop yesterday while running a background terminal build. The, the session hit a proxy prompt hang right in the middle of a script, holding the whole task hostage until I noticed the CLI sitting there, um, waiting for an Enter key press. Total nightmare when you think your background worker is flying through code.

James Turner

That is brutal. But there are a couple quick ways to, you know, diagnose and fix it, right?

Lachlan Reed

Spot on. First off, run slash status in your terminal. You will see a new row called Auto mode server. If server side checks are working, it says Enabled. If your proxy broke the headers and forced a fallback, it, uh, reads Disabled.

James Turner

And if you are stuck behind a locked down corporate proxy where you know you cannot pass custom headers, you do not want that warning interrupting headless scripts or terminal loops every single time.

Lachlan Reed

Right, so you just export CLAUDE CODE AUTO MODE SERVER equals zero in your shell profile or environment variables. That opts you out of asking the server, silences the eligibility warning completely, and keeps your automated tasks running smoothly on client checks.

James Turner

Or if you manage the gateway, just configure it to pass those request headers and payload fields through untouched. Forward the safeguards request field and do not drop safeguard results in the stream, and boom, zero cost classifier checks.

Lachlan Reed

Simple as that. Oh, and speaking of nice quality of life updates, did you catch what landed in 2.1.277 right before this?

James Turner

The, uh, instruction file fallback?

Lachlan Reed

Yes! One AGENTS.md can now brief Claude Code too, in any repo that has no CLAUDE.md.

James Turner

That is huge for multi agent frameworks. If you already have an AGENTS.md set up for other tools, Claude Code just reads it automatically without making you duplicate rules into a CLAUDE.md file.

Lachlan Reed

Less boilerplate, zero classifier overhead, and no more surprise proxy hangs. Fair dinkum, that is how you polish a developer tool.

James Turner

That is the update. Get your proxy headers cleared or export that env var, and enjoy the free classifier runs. See ya!