Claude Code v2.1.304: Plugins, Security, and Auto Mode
Claude Code v2.1.304 was released on October 19, 2026, at 21:34. The update primarily focuses on controlling mods and plugins, security prompts, and a few rather specific edge cases in everyday use. There is not much glamour here. Instead, it delivers things that should ideally work reliably when it matters.
Plugins can no longer simply bypass hooks
The transcript now records when a plugin executed first skips a mod's hook. This makes a process visible that could previously be missing from the log. Especially with multiple extensions, this is not a minor detail, because otherwise it can quickly become unclear why a particular step was not executed.
There is also a new option for tool.check. With decider: "person", only a permission dialog or a host callback can approve the action. The decision therefore does not rest with an automated mechanism. The new e.isReadOnly field also identifies read-only tool calls.
Auto Mode adapts to the project
For operators of their own projects, the /auto-mode-setup command is new. The guided process reads the project and recent sessions to adapt Auto Mode to the respective environment. This sounds less like magic and more like a setup assistant that first looks around before suggesting settings.
According to the release notes, the feature is also available for Bedrock, Vertex, Foundry, Claude Apps Gateway, and sessions with telemetry disabled. Anyone working with different environments can now use the same process for more than just a single configuration.
Also new is /claude-api managed-agents-secure. The command compares a Managed Agent's settings with Anthropic's published security guide. It does not make any changes. In other words, it checks things instead of clearing out the toolbox without being asked.
Security vulnerabilities involving drives and headless runs have been fixed
The version fixes a missing security warning for rm -r on mounted drives or top-level directories. These included /Volumes, /media, and WSL's /mnt/c. The warning was therefore missing precisely in situations where recursive deletion could affect more than just some random subdirectory.
A bug in headless runs has also been fixed. A plugin could extend a run beyond --max-turns, a stop, or the end of input by starting subagents or running already completed subagents again. A specified endpoint was apparently not always the end. This behavior is now among the problems that have been corrected.
Environment settings, API keys, and limits now respond faster too
Further fixes concern the updating of organization settings. After releasing an ANTHROPIC_API_KEY or switching to a custom API key, they are no longer updated only during the hourly refresh. The change should now be taken into account more quickly instead of waiting in the background for a while.
In the Code view on macOS and Linux, Claude Desktop also recognizes exported environment variables from shell startup files such as ~/.zshrc for unsandboxed Bash commands. Anyone who sets such variables there no longer has to worry that the Code view will overlook them entirely.
With LLM gateways, Claude Code retries requests when the context_management field is rejected. This applies to requests for which that field is not accepted. It is a small fallback, but one that can make a noticeable difference in operation.
Pro and Max users also receive a warning when resuming an inactive conversation if doing so would consume a significant portion of their five-hour limit. The warning therefore appears before the potential usage. That may not be spectacular, but it is certainly more pleasant than realizing afterward that an old conversation has suddenly started eating into the quota.
Sources
See more of us in Google search results: add us as a preferred source.
Add as preferred source on GoogleWritten by
Daniel Böhmel has been developing software for over 20 years and has been self-employed since 2007. He started out with interactive web design back in the Flash era; later, he built his own online projects, such as a fitness forum and a supplement store, including the editorial content. Today, his…
View the profile of Daniel BöhmelParticipate now!
Don’t have an account yet? Register yourself now and be a part of our community!