
Claude Code v2.1.152 Major Updates
This page has been translated by machine translation. View original
This is Ishikawa from the Cloud Business Division. Claude Code v2.1.152 was released on May 26, 2026. This update includes new features related to automatic application of code review results to the working tree and skill management, along with numerous bug fixes.
Update Summary
v2.1.152 includes 33 changes. 8 new features including /code-review --fix and skill management (/reload-skills, disallowed-tools), multiple usability and stability improvements, and 16 bug fixes at the core. There are no breaking changes or deprecations.
Note that v2.1.151 was not released (skipped), and the immediately preceding v2.1.150 contained only internal improvements with no user-facing changes. Therefore, v2.1.152 is effectively the most recent release with substantive changes.
Highlights
- New Feature:
/code-review --fixnow directly applies suggestions for reuse, simplification, and efficiency to the working tree after review. Additionally, the/reload-skillscommand anddisallowed-toolsspecification for skills/slash commands have been added, improving skill operation workflows. - Bug Fix: An issue where sessions would become unresponsive after switching models or logging in has been resolved.
Update Details
New Features
/code-review --fixworking tree application:/code-review --fixnow directly applies suggestions for reuse, simplification, and efficiency to the working tree after review. Additionally,/simplifynow internally calls/code-review --fix(as an alias).disallowed-toolsfront matter: Skills and slash commands can now specifydisallowed-toolsin their front matter, allowing specific tools to be excluded from the model while that skill is active./reload-skillscommand: A/reload-skillscommand has been added that rescans the skills directory without restarting the session.- Skill reloading via
SessionStarthook: When theSessionStarthook returnsreloadSkills: true, skills installed by the hook become available within the same session. - Session title setting via
SessionStarthook: At startup or resume, theSessionStarthook can now set the session title viahookSpecificOutput.sessionTitle. MessageDisplayhook event: A new hook eventMessageDisplayhas been added that can transform or hide the text of displayed assistant messages.pluginSuggestionMarketplacesadmin setting: An admin setting that allows administrators to allowlist organization marketplaces for plugins suggested in context-sensitive hints.- OpenTelemetry attribute
app.entrypoint: The session entrypoint can now be added as an OpenTelemetry metrics attribute (opt-in viaOTEL_METRICS_INCLUDE_ENTRYPOINT=true).
Improvements
- Automatic fallback to
--fallback-model: Instead of failing every request when the primary model is not found, the session now switches to the configured--fallback-modelfor the remainder of the session. - Auto mode no longer requires opt-in: Auto mode can now be used without prior opt-in consent.
/usagesupport for large session files: Large session files are now included in/usagebreakdowns. Files are read via streaming, keeping memory usage constant.- Improved thinking summary display: Thinking summaries inside collapsed groups now remain readable for at least 3 seconds, are rendered as markdown, and are truncated at 10 lines (press
Ctrl+Oto view the full content). - Live "Thinking for Ns" display: In fullscreen mode, the thinking time display now counts up live during thinking and retains its value if interrupted midway.
- Simplified Workflow tool progress display: The live agent count is now displayed only in the persistent workflow status line below the prompt.
- Background processing waiting indicator: The post-response timer now shows a waiting state when background agents/workflows are running, and reports the cumulative time after results are processed.
--scopesupport formarketplace remove:claude plugin marketplace removenow accepts--scope user|project|local, bringing it in line withadd/install/uninstall.- Vim mode history search: In NORMAL mode,
/now opens reverse history search (likeCtrl+R), matching bash/zsh vi-mode behavior.
Fixes
The main bug fixes are as follows.
- Fixed session becoming unresponsive: Fixed an issue where stale thinking block signatures remaining in history after switching models or logins caused sessions to stall (signatures are now proactively removed, with a retry safety net added).
- Fixed terminal display degradation in long sessions: Fixed an issue where terminal styles degraded during long sessions by reusing the renderer's style pool.
- Fixed sandbox-enabled warning not displaying: Fixed an issue where the sandbox-enabled warning was not shown in the compact launch display, ensuring it now appears in all layouts.
- Fixed incorrect deduplication of plugin MCP servers: Fixed an issue where plugin MCP servers with the same command but different environment variables were incorrectly deduplicated.
- Fixed git branch-tracking plugin stopping updates: Fixed an issue where plugins tracking git branches stopped receiving updates after the plugin registry was rebuilt.
- Fixed remote MCP connection failures: Fixed an issue where remote MCP servers failed to connect in Claude Code Remote sessions when an egress proxy was enabled.
- Fixed background crash in
claude agents: Fixed an issue where background workers crashed when an old permission prompt was accepted after a subagent was cancelled. - Fixed
cache_creation_input_tokensshowing as 0: Fixed an issue wherecache_creation_input_tokensappeared as 0 in transcript and result usage when the API reported cache writes only in nestedcache_creationbreakdowns. - Additionally, numerous minor bugs have been fixed, including loading spinner display, markdown table rendering, false reports from
/doctor, the effort change confirmation dialog, and push notification detection logic.
Closing
v2.1.152 is an update that adds new features such as working tree application for /code-review --fix and skill management capabilities, along with fixes for session stalling and issues around MCP and plugins. Since there are no breaking changes or deprecations, you can update without worrying about impact on existing workflows. If you regularly use skills, plugins, or code review features, this update has a broad impact on your workflow — why not update and give it a try?
References
