Anthropic: Claude Code v2.1.163 — version-locking, /plugin list, and hook improvements
Anthropic released Claude Code v2.1.163 with Managed Settings for enterprise version-locking, a new /plugin list command, and improvements to the Stop and SubagentStop hooks. The release also brings several practical additions and a series of bugfixes, including a fix for hook conditions that incorrectly triggered on every Bash command.
This article was generated using artificial intelligence from primary sources.
Anthropic released Claude Code v2.1.163 on June 4, 2026, a release that introduces enterprise version-locking via Managed Settings, a new /plugin list command, and improvements to the Stop and SubagentStop hooks, along with a series of bugfixes. The release date is confirmed by GitHub (published_at 2026-06-04T21:52:51Z).
How does enterprise version-locking work?
The most significant novelty is Managed Settings with the parameters requiredMinimumVersion and requiredMaximumVersion. With them, Claude Code refuses to start if the installed version is not within the allowed range. For enterprise environments, this means the ability to lock versions — administrators can ensure that all team members use an approved version range, avoiding incompatibilities and uncontrolled updates.
What does the new /plugin list command offer?
The release adds a /plugin list command with --enabled and --disabled filters. Users can thus quickly review the list of plugins and distinguish active ones from disabled ones. This makes configuration management easier, especially in environments with a larger number of installed plugins.
How were the hooks improved?
The Stop and SubagentStop hooks can now return hookSpecificOutput.additionalContext. This way the hook continues the turn instead of being marked as a hook error — that is, the hook can inject additional context into execution without interrupting the workflow. This expands automation possibilities, as hooks become a source of context rather than just a point of interruption.
What other additions were introduced?
The release also brings several practical improvements: the “c to copy” shortcut in /btw, $ escape syntax in skills, and the CLAUDE_CODE_SESSION_ID environment variable for stdio MCP servers when using --resume. These additions target everyday ergonomics and better integration with MCP servers when resuming sessions.
Which bugs were fixed?
The list of bugfixes covers several scenarios. Fixed are a freeze of claude -p with backgrounded commands and an “ANTHROPIC_API_KEY required” error on Bedrock, Vertex, and Foundry under CI=true. Windows EEXIST/OneDrive errors were resolved. Particularly notable is the fix for hook conditions if: "Bash(...)" that incorrectly triggered on every Bash command containing $() or $VAR — the condition is now evaluated correctly. This set of fixes makes v2.1.163 more stable in CI environments and on Windows.
Frequently Asked Questions
- What does version-locking bring in Claude Code v2.1.163?
- Managed Settings now support `requiredMinimumVersion` and `requiredMaximumVersion`. Claude Code refuses to start if the version is not within the allowed range, which lets enterprise teams lock down the permitted versions of the tool.
- What is new with the /plugin command?
- A new `/plugin list` command has been added with `--enabled` and `--disabled` filters, making it easier to review which plugins are active and which are disabled.
- How were the Stop and SubagentStop hooks improved?
- The Stop and SubagentStop hooks can now return `hookSpecificOutput.additionalContext` to continue the turn without being marked as a hook error. This way a hook can add context instead of interrupting execution.
Related news
Anthropic: Claude Code v2.1.183 Blocks Destructive Git and Infrastructure Commands in Auto Mode
AWS: SageMaker Gets Over 100 Detailed Inference Metrics and an Insights Dashboard on CloudWatch
GitHub: Copilot Retires Opus 4.6 (fast) on June 29, Adds AGENTS.md to Code Review and ai_credits_used Field to API