Claude Code 2.1.283: Auto Mode by Default

James Turner

If you updated Claude Code to version 2.1.283 this week, and you run it through Amazon Bedrock, Google Cloud Vertex AI, or with telemetry turned off, something pretty dramatic just shifted under your feet. Your interactive terminal sessions are now booting straight into auto mode by default.

Lachlan Reed

Yeah, straight into the deep end! No prompt asking for permission to read a folder, no tap on the shoulder. Just straight to work. The changelog notes put it plainly: interactive sessions on third party providers or with telemetry off start in auto mode when no permission mode is configured.

James Turner

Which is wild if you are sitting inside an enterprise VPC expecting manual control. But you know why they did it, right? Prompt fatigue was completely choking developer velocity on those third party endpoints. Every single file inspect, every git status, you had to hit enter to approve.

Lachlan Reed

Oh, mate, totally. It was like driving with the handbrake on. You ask it to scan a repo, and it stops every two seconds asking, can I peek at package dot json? Can I check git status? But, but, here is the rub. If a developer isn't expecting it, seeing your terminal run shell commands on its own without a prompt gives you quite the fright.

James Turner

Right, but auto mode does not mean total anarchy. It uses a classifier to separate routine, read only actions from destructive things like deleting files or pushing commits. The classifier grants automatic passes to safe reads, but still pauses and prompts you for risky mutations.

Lachlan Reed

True, but if your company policy mandates human confirmation on every single step, having an update quietly flip that default could rattle some cage doors in compliance. If you want the old manual behavior back, how do you pin it down?

James Turner

Super straightforward. You just open your settings dot json in your dot claude folder, and set permissions, defaultMode, to default. That locks it back to manual approvals. Or, if you are mid session and Claude starts running too fast, just hit Shift plus Tab to cycle back to manual mode on the fly.

Lachlan Reed

Shift plus Tab, easy as. And you can run slash status in your console to inspect what the auto mode classifier is actually up to. Which brings up a sneaky gotcha for cloud proxies, doesn't it?

James Turner

Yes! That is a huge detail. If your corporate proxy strips custom gateway headers, Claude Code might fail over to evaluating auto mode locally, which burns extra input tokens against your Bedrock or Vertex model quota instead of using the fast server side classifier. You have to keep an eye on that CLAUDE CODE AUTO MODE SERVER setting.

Lachlan Reed

Sneaky token costs, nobody wants that on their cloud bill at the end of the month. Now, what about the other goodies tucked into 2.1.283? Because there are some absolute gems in here.

James Turner

The MCP image change! Before this, if a Model Context Protocol tool generated an image, say a UI test screenshot or a data plot, it stayed trapped in the tool payload. Now, Claude Code automatically saves MCP returned images directly to disk files.

Lachlan Reed

That is massive. That means your local Bash scripts, or Claude's built in Read tool, can immediately pick up the file, inspect the bytes, or pass it down a build pipeline. It turns visual tool outputs into real workspace artifacts.

James Turner

And there is a really handy change for flags: system prompt and append system prompt now let you pass both raw text and a file path simultaneously. It automatically prepends the file content before your inline string. So you can load a base company instruction file and slap a quick session specific override on the end.

Lachlan Reed

And thank goodness for the Windows fix! On PowerShell, previous builds had a scary edge case where running cmd slash c rd or rmdir could bypass checks and let things delete drive roots or user profile folders. They patched that right up so PowerShell refuses to touch root directories.

James Turner

Yeah, not accidentally wiping C drive is definitely a quality of life improvement.

Lachlan Reed

Too right, mate. Alright, go check your settings files and mind those auto permissions. Catch you next time.