Agent Upstart

Cool things people are building with agents — and practical help getting the most out of them.

Playbooks · Coding tasks

Claude Code 2.1.328 makes auto mode the cloud default

Written November 19, 2026

Claude Code 2.1.328 starts Opus 4.6 and Sonnet 4.6 sessions in auto mode on Bedrock, Agent Platform, Foundry and the gateway, and lets hooks block MCP calls.

Claude Code 2.1.328 arrived on November 19, 2026, and its biggest change is one your terminal will not announce. The v2.1.328 release notes add auto mode for Claude Opus 4.6 and Sonnet 4.6 on Amazon Bedrock, Google Cloud's Agent Platform, Microsoft Foundry and the Claude apps gateway — and interactive sessions with no permission mode set start in it. If your team runs Claude Code through one of those four routes, an ordinary update changes how far Claude goes before it asks you. The same release gives hooks a new way to stop an MCP tool call, and warns about two places where messages and telemetry can vanish.

Auto mode becomes the starting mode

Until now, a session with no permission mode set opened in the standard mode, where Claude asks before it acts. On the four cloud routes above, that default is now auto mode for Opus 4.6 and Sonnet 4.6. Nothing in the session announces the switch; you learn it from the release notes, or from watching Claude work further into a task before pausing. The change is scoped: it names those four platforms and those two models. A related change reaches the prompts — plan mode and Bash prompts for Opus 4.6 and Sonnet 4.6 on third-party providers now use and offer auto mode, as on newer models, and a disableAutoMode setting turns both off. If your permission policy assumed the old default, revisit it under this release.

Hooks can block an MCP call that fails

A mcp_tool hook can now carry "onFailure": "block", as command and HTTP hooks already could: when the hook's own call fails, the action it guards is blocked rather than waved through. A hook that exists to screen MCP calls — judging a server, a payload, a destination — had a gap exactly when it broke: the screening failed, and the call it was meant to judge went ahead anyway. With the block setting, a failed hook stops the action instead: a guard that fails closed instead of open.

Two warnings about things that vanish

The first is a warning when a message from a session that skips permission prompts may be held and dropped by a cloud session — a message sent into a session that never asks can now be flagged as at risk instead of disappearing silently. The second concerns telemetry: a notice now appears in /status and in claude doctor when an OpenTelemetry exporter has no endpoint and its data would likely be lost. If the destination was never configured, the exporter has been collecting into a void; the notice names the problem where an operator is likely to look.

A host can stop a deferred tool call from resuming

A new environment variable, CLAUDE_CODE_DISABLE_DEFERRED_TOOL_RESUME, lets a host stop claude -p --resume and --continue from running a tool call a hook deferred. A deferred call is one a hook held back rather than letting run; without the variable, resuming the session could run it later, away from the moment the hook judged it. Hosts that embed or supervise Claude Code now get a switch to say a deferred call stays deferred — a new control over what a resume is allowed to revive.

Fixes that protect saved work and counts

The fix list is long, and four items protect things you already have. Automatic compaction now rebuilds the system prompt the way /compact does, instead of reusing the session's earlier one. Saving a scheduled task no longer erases the project's other saved tasks when the scheduled tasks file can't be read — and a task with a typo in that file is no longer deleted on the next save. Bash commands in zsh no longer stop with a "not found" error at a word starting with =, such as echo ====. And the token counts on the spinner and for subagents are fixed: they had counted a retried reply twice, missed replies that were not streamed, and stood still while Claude was thinking.

Self-hosted runners, in brief

Operators of self-hosted runners get their own additions: a --repository-folder flag naming the folder sessions use for a repository, a --hook-label flag and a --metadata option that both hand session labels to the spawn-runner hook, two orchestrator metrics covering queue waits and sessions given up on, and a start-up warning when the host's settings file sets a default permission mode that sessions ignore.

What to do

The previous release in this line is covered in the page linked below.

Related playbooks

Sources

Back to: Coding playbooks hub · Also: Claude Code 2.1.327 lists broken setup files