Playbooks · Coding tasks
Claude Code 2.1.323: Code Mode writes the tool calls
Written November 13, 2026
Code Mode lets Claude write JavaScript to call its own tools. Plus the 1M default for unknown models, and plugin version gating.
What changed
Claude Code 2.1.323, published November 12, is a large release: a new experimental way for Claude to call its tools, a context-window default that changes how gateway and third-party model sessions behave, and version gating for plugins. The notes also carry a long run of sandbox and permission fixes. Three of the changes can alter a working setup on the day you update, so they come first here.
Code Mode: Claude writes the calls
The headline addition is Code Mode, described in the notes as an experimental opt-in in which Claude writes JavaScript to call its tools. Instead of issuing tool calls one at a time, the model can put the calls into a script. The release points to a Code Mode page at code.claude.com for turning it on, and for turning it off for an organization. That page returns a 404, so the enable steps, the list of tools a script can reach, and the sandbox around the script are not public yet. What the notes do establish is the shape of the control: the feature is off unless someone turns it on, and an organization can turn it off for its members. Until the documentation lands, that off switch is the part an admin can act on.
The 1M default for models Claude Code does not know
The second change is quieter and more likely to bite. The context window assumed for a model ID that Claude Code does not recognize is now 1M tokens, up from 200K. For sessions running on other vendors' models with a smaller real window, the notes spell out the failure: once the session fills past the model's true limit, it can fail every turn until you run /clear. Two controls are named. Use /autocompact to compact earlier, or set CLAUDE_CODE_DISABLE_1M_CONTEXT=1 to keep the old 200K assumption. Anyone routing Claude Code through a gateway or a custom model ID should set that variable before the first long session on 2.1.323, not after a stuck one.
Plugins get version ranges, validation gets teeth
Plugins can now declare engines["claude-code"] in plugin.json. A plugin outside its stated Claude Code version range is not installed, updated, or loaded, and install and update pick the newest version that fits the range. For plugin authors, claude plugin validate now type-checks the plugin's TypeScript hooks module: each finding is a warning, and --strict turns those warnings into failures. Authors who publish hooks in TypeScript can run validation in CI with --strict and catch hook errors before a release instead of at load time.
Sandbox and permission fixes
The fix list is long, and the permission items matter most:
- Bash permission prompts no longer offer a "don't ask again" option for commands that write to sensitive paths such as
.gitor.claude, where the saved rule did not stop the next prompt anyway. - A case where Bash permission checks judged an
rmfrom the wrong folder, and skipped the dangerous-removal prompt, is fixed. - When auto mode is unavailable,
--permission-mode autoand a settingsdefaultMode: autonow start in Manual mode, which asks first, instead of a mode that could allow more. - The Bash sandbox could switch off during a session; that case is fixed, as is a case where
sandbox.excludedCommandslet an unnamed command run outside the sandbox. - Wildcard allow rules, such as
Bash(ls*), no longer skip the prompt in some cases, and a rule that names a variable now asks.
Two smaller additions round out the release: a progress heartbeat every 30 seconds while hooks run long in claude -p and SDK sessions, so a host does not end the turn as hung, and CLAUDE_CODE_DISABLE_AGENT_PROGRESS_SUMMARIES, which turns off subagent progress summaries and the requests that write them.
What to do
Update normally if you run Anthropic's own models and no plugins with narrow version needs. Before updating a gateway or third-party-model setup, set CLAUDE_CODE_DISABLE_1M_CONTEXT=1 unless you know every model ID in play really has a 1M window. Plugin authors should add an engines range and run claude plugin validate --strict. And leave Code Mode alone until its documentation page exists; the notes give no supported way to evaluate it yet.
Related playbooks
- Claude Code 2.1.322: Vertex fast mode, three regions
- Claude Code 2.1.328 makes auto mode the cloud default
- Confine Claude Code writes to your project
- Antigravity CLI 1.5.4: ACP Auto mode
Sources
Back to: Coding playbooks hub · Also: Claude Code 2.1.321: Fable 5.2 is default · Claude Code 2.1.319: unattended runs stop stalling · Claude Code 2.1.322: Vertex fast mode, three regions