Friday, 13 November 2026, story 2 of 7
Claude Code 2.1.323 adds opt-in Code Mode and plugin version gating
The 12 November release makes Code Mode an experimental opt-in and stops plugins outside their stated Claude Code version range from loading.

What happened
Claude Code v2.1.323, released on 12 November, adds Code Mode, an experimental opt-in in which Claude writes JavaScript to call its tools. The release notes point to the documentation for turning it on, or off for an organization. They give no detail on pricing or rollout.
The release also adds an engines["claude-code"] field to plugin.json. Plugins outside their stated Claude Code version range are not installed, updated or loaded, and install and update pick the newest version that fits. The release also carries many fixes, among them several to Bash permission checks and the sandbox.
What it means
Code Mode changes how Claude calls tools, but the notes do not say what it is for or how well it works, so there is no basis yet to judge any benefit. Because it is opt-in and can be switched off for an organization, the first decision likely falls to admins.
Plugin gating matters more day to day. A plugin that states a Claude Code range will now stop loading when the installed version falls outside it, so authors who set a range need to keep it current.
The security fixes deserve a read. Bash allow rules with an attached wildcard skipped the permission prompt in some cases, and teams that rely on such rules may see more prompts after updating.
What to do: Decide whether your organization wants Code Mode, check plugin version ranges, and review wildcard Bash allow rules, which now prompt in some cases.
Source
- v2.1.323, Claude Code releases
Filed under Coding tools. Published .
"What it means" is analysis, not reporting. Found an error? Write to daily@vibitely.com.