Every Diff about Claude Code: the model, pricing, limit and feature changes that alter how you ship with an agent, newest first, each with its official source. 8 notes so far; the newest is from November 9, 2026. Written by MK.
Claude Code 2.1.321 makes Fable 5.2 the default Fable model and moves saved 5.1 picks to it. Mods Claude writes now turn on without asking in auto and bypass modes.
score prompts raised by a mod's own tool calls: "0"
- Claude Code 2.1.321, released November 9, adds Fable 5.2 as the default Fable model at $8/$40 per MTok with 1M context
- Saved Fable 5.1 picks move to fable, at once on Pro and Max, on Team and Enterprise once the organization allows it
- Mods Claude writes turn on without asking in auto and bypass modes and do not load in dontAsk mode
- A mod's own tool calls raise no permission prompt, even under ask rules, while deny rules and organization policy still apply
- Affects Claude Code users on Fable and anyone relying on ask rules to gate mods
open the article →
What changed
Claude Code 2.1.321, released November 9, adds Claude Fable 5.2 as the default Fable model: 1M context, $8/$40 per MTok. Saved Fable 5.1 picks move to fable, at once on Pro and Max plans and on Team and Enterprise once the organization allows it; /model claude-fable-5-1 switches back. Mods Claude writes now turn on without asking in auto and bypass modes, and do not load in dontAsk mode. A mod's own tool calls raise no permission prompt, even under your ask rules or in dontAsk and -p runs; deny rules and organization policy still apply.
Why it matters if you ship with an agent
Pro and Max users who saved Fable 5.1 are on 5.2 after the update, so check the model line before a long run. Ask rules no longer cover what a mod calls; anything a mod must never do belongs in a deny rule.
sources: github.com
open the article →
Claude Code 2.1.319 adds permissions.denyInsteadOfPrompting, and auto mode with telemetry or feature flags off now asks or denies with no built-in classifier fallback.
score fallback classifiers: "0"
- New setting denyInsteadOfPrompting denies any call that would wait on a prompt and the turn continues
- Applies in terminal sessions, subagents and teammates
- Auto mode with telemetry or feature flags off, or behind an LLM gateway, asks or denies when the server cannot check, no classifier fallback
- CLAUDE_CODE_AUTO_MODE_SERVER=0 keeps the classifier, and claude -p now exits 1 when actions are refused
- Affects unattended Claude Code runs, gateway users and anyone with telemetry off
open the article →
What changed
Claude Code 2.1.319, out November 6. A new permissions.denyInsteadOfPrompting setting denies any tool call that would wait on a permission prompt, and the turn continues, in terminal sessions, subagents and teammates. Auto mode with telemetry or feature flags off, including behind LLM gateways, now asks about or denies calls the server cannot check, with no fallback to the built-in classifier; CLAUDE_CODE_AUTO_MODE_SERVER=0 keeps the classifier, and Bedrock, Vertex and Foundry are unchanged. claude -p exits 1, not 0, when auto mode refuses actions because no safety check was available.
Why it matters if you ship with an agent
Unattended runs that hung on a prompt can now fail fast; turn the setting on and read the denials afterwards. Gateway users with telemetry off should expect prompts where auto mode used to decide. Scripts that watched claude -p for exit 0 get a 1 now.
sources: code.claude.com
open the article →
Claude Code 2.1.318 stops a flagged subagent instead of switching its model, no longer installs the IDE extension from an IDE terminal, and widens MCP deny lists.
score minutes before a background subagent's shell command is backgrounded: "3"
- Claude Code 2.1.318, out November 4.
- With "Switch models when a message is flagged" on "Ask each time", a subagent now stops instead of switching models.
- An unattended run whose subagent gets flagged now stops rather than finishing on another model; check jobs that counted on the switch.
open the article →
What changed
Claude Code 2.1.318, out November 4. With "Switch models when a message is flagged" on "Ask each time", a subagent now stops instead of switching models. Starting in an IDE terminal no longer installs or updates the IDE extension; use /ide from another terminal. A deniedMcpServers URL entry now also blocks Anthropic-provided servers at that upstream URL, and connectors in cloud and self-hosted sessions. Agents created by /claude-api managed-agents-onboard get the auto permission policy by default. Background subagents move a shell command to the background after 3 minutes on all providers.
Why it matters if you ship with an agent
An unattended run whose subagent gets flagged now stops rather than finishing on another model; check jobs that counted on the switch. Audit MCP deny lists: a URL rule now takes Anthropic's own server at that address too. A long test run inside a background subagent is backgrounded at 3 minutes, so poll for the result. The extension stops updating itself from the terminal.
sources: code.claude.com
open the article →
Claude Code 2.1.317 adds a check before a web or shell call sends your account email, and subagents on another model stop inheriting the session's effort.
score session effort levels your subagents inherit: "0"
- Claude Code 2.1.317, released November 3, asks before a web or shell tool call sends your account email address to the network.
- Subagents and teammates on a different model from the main conversation now use that model's saved effort level, or its default, instead of the session's effort level.
- Headless runs are the thing to check.
open the article →
What changed
Claude Code 2.1.317, released November 3, asks before a web or shell tool call sends your account email address to the network. Subagents and teammates on a different model from the main conversation now use that model's saved effort level, or its default, instead of the session's effort level. Agent SDK hook callbacks can set onFailure: "block", so a callback that fails blocks the action instead of letting it run.
Why it matters if you ship with an agent
Headless runs are the thing to check. A claude -p job whose curl or git command carries your account email now hits a new check, and a headless job has nobody to answer it, so run those jobs once by hand after upgrading. If your session runs at high effort and your subagents on a cheaper model, those subagents just dropped to that model's own setting; set it per model if you were counting on the inherited one. SDK hook authors: a hook that errors still lets the action run unless you set the block option.
sources: code.claude.com
open the article →
Claude Code 2.1.316 deprecates fast mode on Opus 4.8 as of October 30, 2026. From November 30 those requests error with no fallback. Move to Opus 5.5.
score days of notice: 31
- Claude Code 2.1.316 (October 31) deprecates fast mode for Claude Opus 4.8 as of October 30, 2026, with removal on November 30, 2026.
- After removal, a fast mode request on Opus 4.8 returns an error and does not fall back to standard Opus 4.8.
- If Claude Code runs Opus 4.8 with fast mode on, or a script sets speed to fast on claude-opus-4-8, it stops on November 30 with an error, not a slower answer.
open the article →
What changed
Claude Code 2.1.316 (October 31) deprecates fast mode for Claude Opus 4.8 as of October 30, 2026, with removal on November 30, 2026. After removal, a fast mode request on Opus 4.8 returns an error and does not fall back to standard Opus 4.8. The advice is to migrate to Opus 5.5 to keep the speedup. The fast mode docs carry the same warning.
Why it matters if you ship with an agent
Days of notice: 31. If Claude Code runs Opus 4.8 with fast mode on, or a script sets speed to fast on claude-opus-4-8, it stops on November 30 with an error, not a slower answer. Move those to Opus 5.5, where fast mode needs no beta header and the docs price it at $8 per million input tokens and $40 per million output, against $10 and $50 for Opus 4.8. Fast and standard speeds do not share the prompt cache, so watch the bill after the move.
sources: code.claude.com
open the article →
Claude Code 2.1.305 stops allowedMcpServers filtering managed-mcp.json stdio servers that use ${VAR} only in env, so one you left out now loads on upgrade.
score allowlist rules that still block it: "0"
- Claude Code 2.1.305, released October 20, changes how allowedMcpServers applies to managed-mcp.json.
- Stdio servers that use ${VAR} only in env are no longer filtered by the allowlist: a server your allowlist left out loads on upgrade, and deniedMcpServers is the way to keep it off.
- If an admin pushes managed-mcp.json and your allowlist was doing the filtering, a server you never approved loads after this upgrade.
open the article →
What changed
Claude Code 2.1.305, released October 20, changes how allowedMcpServers applies to managed-mcp.json. Stdio servers that use ${VAR} only in env are no longer filtered by the allowlist: a server your allowlist left out loads on upgrade, and deniedMcpServers is the way to keep it off. Plugins that Claude Desktop mounts by path no longer keep their allowed-tools when managed settings set allowManagedPermissionRulesOnly. A new sandbox.allowNestedUserNamespaces setting lets sandboxed commands on Linux create user namespaces, for Chromium and rootless podman, which lets them get around the sandbox's file protections.
Why it matters if you ship with an agent
If an admin pushes managed-mcp.json and your allowlist was doing the filtering, a server you never approved loads after this upgrade. Run claude mcp list after updating and add a deniedMcpServers entry for anything that should stay off. Leave the nested-namespaces setting alone unless a sandboxed command needs it; it opens the file protections by design.
sources: code.claude.com
open the article →
Claude Code 2.1.300 makes remote-control --sandbox an error and validates hook-rewritten tool input: unknown keys dropped, rejected input denies the call.
score flags that ever worked: "0"
- Claude Code 2.1.300, dated October 14, removes --sandbox and --no-sandbox from claude remote-control.
- They had no effect; passing either now exits with an error, and sandbox.enabled in settings is how you sandbox a session.
- Grep your launch scripts for remote-control --sandbox; that line now fails instead of being ignored.
open the article →
What changed
Claude Code 2.1.300, dated October 14, removes --sandbox and --no-sandbox from claude remote-control. They had no effect; passing either now exits with an error, and sandbox.enabled in settings is how you sandbox a session. The updatedInput a PreToolUse or PermissionRequest hook returns is now validated like Claude's own input: unknown keys are dropped, and input the tool rejects denies the call. Large requests to api.anthropic.com now use gzip even with telemetry off; CLAUDE_CODE_GZIP_REQUEST_BODIES=0 turns it off.
Why it matters if you ship with an agent
Grep your launch scripts for remote-control --sandbox; that line now fails instead of being ignored. If a hook rewrites tool input, a misspelled key is now dropped and a value the tool rejects denies the call, so run your hooks on a scratch repo before the next headless job. If a proxy between you and api.anthropic.com chokes on compressed bodies, set the gzip variable to 0.
sources: code.claude.com
open the article →
Claude Code 2.1.299 makes an mcpa allow rule match only the server a. Servers named ab or a_ need their own mcp * rule, in agent tools lists too.
score servers one rule reaches: "1"
- Claude Code 2.1.299, dated October 14, narrows MCP permission rules.
- An allow rule like mcpa now reaches only the server named a, not one named ab or a_.
- A rule that was quietly covering a sibling server now prompts for its tools, and a non-interactive run cannot answer a prompt.
open the article →
What changed
Claude Code 2.1.299, dated October 14, narrows MCP permission rules. An allow rule like mcp__a now reaches only the server named a, not one named a__b or a_. To allow those, write mcp__<server>__* with the server's whole normalized name. Agent tools: lists take only the named server's tools, with the same spelling for names that contain __. The release also fixes deny and ask rules that were not applying to servers with a double underscore in their normalized name.
Why it matters if you ship with an agent
A rule that was quietly covering a sibling server now prompts for its tools, and a non-interactive run cannot answer a prompt. Check every mcp__ rule in settings.json and agent frontmatter against claude mcp list, and respell the ones for servers with __ or a trailing _ in the name. Deny rules on those servers may only have started working today.
sources: code.claude.com
open the article →