Anthropic News | Version Control Settings in Claude Code 2.1.163
On the morning of June 6, 2026, the Clauder Navi editorial team brings you the latest official Anthropic updates. Today there are no new company announcements, research reports, or policy news — the spotlight is entirely on two releases of the developer tool Claude Code. The main release is v2.1.163, published on June 4, which introduces version range control settings for administrators, adds the /plugin list command, and includes several permission-related bug fixes. The follow-up v2.1.165 is a maintenance release focused on stability. Read on for a breakdown of each item.
The biggest news on June 6, 2026 is the release of developer tool Claude Code v2.1.163 (released at 21:52 JST on June 4). The headline feature is the addition of requiredMinimumVersion / requiredMaximumVersion, which lets administrators specify the permitted version range — Claude Code will refuse to launch if the installed version falls outside that range. This means keeping every team member on a minimum version is now just a matter of configuration.
On the feature side, the release also adds /plugin list to display installed plugins, changes stop hooks (Stop / SubagentStop) so they can return additional context without being treated as errors, and introduces a \$ escape syntax to handle dollar signs before numbers in skill bodies as literal characters. There are also numerous permission-related fixes, including a bug where deny rules were not being applied to paths under the home directory and another where organization permission rules were not applied at startup.
v2.1.165, released the following morning on June 5, contains only "bug fixes and stability improvements" with no individual items listed. It is a maintenance release following the many fixes in the preceding version — simply updating to the latest is sufficient. Today has no new company, research, or policy announcements; it is a day to catch up on practical developer tool updates.
目次 (6)
- [1] Claude Code v2.1.163: New Admin Settings to Enforce Version Range
- [2] Other New Features in v2.1.163 — /plugin list, Stop Hook Context, and \$ Escaping
- [3] Key Bug Fixes in v2.1.163 — Permission Rules, Deny Rules, and Freeze Issues
- [4] Claude Code v2.1.165: Maintenance Release with Bug Fixes and Stability Improvements
- What to Watch Next
- Sources
[1] Claude Code v2.1.163: New Admin Settings to Enforce Version Range
The developer tool Claude Code released v2.1.163 at 21:52 JST on June 4, 2026. Source: claude-code v2.1.163 release notes.
The most notable addition in this release is administrator-configurable settings to restrict which versions can be used. requiredMinimumVersion sets the lower bound and requiredMaximumVersion sets the upper bound; Claude Code will refuse to launch if the version is outside the specified range. This is not version control in the git sense — it is a mechanism for organizations to define which versions of Claude Code itself are permitted.
Impact for engineer readers: ★★. This is practical for any team or organization that wants to standardize on a particular version. The long-standing challenge of ensuring every team member stays on a minimum version — previously dependent on each individual's update habits — can now be enforced through a single configuration setting. Seen in the context of the permission and operational improvements that have been rolling in since v2.1.161 / v2.1.162, this marks steady progress in building out the infrastructure for team-wide adoption.
[2] Other New Features in v2.1.163 — /plugin list, Stop Hook Context, and \$ Escaping
Beyond the version control settings, v2.1.163 includes several other new features that improve day-to-day use. Source: claude-code v2.1.163 release notes.
/plugin listcommand — Displays all installed plugins, with support for filtering by enabled/disabled status, making it easy to see exactly which plugins are active.- Stop hook context return — Stop hooks (Stop / SubagentStop) can now return additional context without being treated as errors, giving developers who build custom integrations greater expressiveness.
\$escape syntax — Dollar signs before numbers in skill bodies are now treated as literal characters, preventing accidental interpretation of currency amounts as variables./btwcopy shortcut — The/btwcommand, which lets you insert an aside question mid-conversation, now has a shortcut to copy the raw Markdown withc.
Impact for engineer readers: ★★. Each of these is a small addition, but together they address real friction points: plugin visibility, integration expressiveness, notation pitfalls, and workflow convenience.
[3] Key Bug Fixes in v2.1.163 — Permission Rules, Deny Rules, and Freeze Issues
In addition to new features, v2.1.163 includes a substantial number of bug fixes that matter in production environments. Source: claude-code v2.1.163 release notes.
The main fixes are as follows:
- Deny rules not being applied to paths under the home directory
- A freeze occurring after the final result when background processes had not yet exited
- A regression (introduced in v2.1.154) that prompted for an API key during continuous integration in certain cloud execution environments
- Command failures in certain build environments or under security hardening
- Organization permission rules not being applied when startup fetching completed at the wrong timing
- Keyboard input becoming unresponsive after a paste operation
Impact for engineer readers: ★★. The fixes to deny rules and permission rules are especially significant, as they directly affect the security of environments where the permitted scope of operations is strictly controlled. Teams that rely on blocking out-of-scope operations will see the most benefit from this update.
[4] Claude Code v2.1.165: Maintenance Release with Bug Fixes and Stability Improvements
Shortly after, v2.1.165 was released at 05:45 JST on June 5, 2026. Source: claude-code v2.1.165 release notes.
The only listed change is "bug fixes and stability improvements" — no individual items are specified. This appears to be a maintenance release following the numerous fixes in v2.1.163. Note that v2.1.164 does not appear in the release list and may be a skipped version number.
Impact for engineer readers: ★. As a stability release with no itemized changes, simply updating to the latest version is all that is required. There is no major new information here, but applying it alongside v2.1.163 gives you full coverage of the recent improvements.
What to Watch Next
Today saw no new company announcements, research, or policy news — updates were confined to practical developer tool improvements. Across v2.1.161 / v2.1.162 through v2.1.163 / v2.1.165, Claude Code has been receiving steady attention in the areas of permission rule refinement, prevention of accidental operations, and team-level governance. The next things to watch are how the newly added version control settings get adopted in organizational deployments, and how much further stability improves in upcoming releases — including whether the apparently skipped v2.1.164 surfaces. The Clauder Navi editorial team will continue tracking developments across company, product, and developer tools.
Sources
- Claude Code v2.1.163 release notes: https://github.com/anthropics/claude-code/releases/tag/v2.1.163
- Claude Code v2.1.165 release notes: https://github.com/anthropics/claude-code/releases/tag/v2.1.165
