Anthropic News | Claude Code v2.1.147/148 Bash Fix
Have you ever updated Claude Code only to find that all your Bash commands suddenly stopped working? This article covers two official Anthropic releases dated May 23, 2026 (JST): the emergency hotfix v2.1.148, which patched the exit code 127 regression introduced in v2.1.147 in under five hours, and v2.1.147 itself, which includes features such as /code-review --comment support for posting inline comments to GitHub PRs.
The most critical topic today is the emergency hotfix Claude Code v2.1.148. This single-bug-fix release patched the regression introduced in v2.1.147 the previous night — where the Bash tool returned exit code 127 (command not found) for all commands for some users — in under five hours. Any user whose shell commands stopped working entirely after installing v2.1.147 must upgrade to v2.1.148 immediately. Environments with automatic updates disabled are advised to update manually.
The consecutively released v2.1.147 added the /code-review --comment option to review-related commands, enabling inline comments to be posted directly to GitHub PRs from the CLI. Effort-level specification (e.g., /code-review high) is also retained, making the workflow of invoking claude --code-review from CI to post comments on a PR simpler than ever. Background sessions now remain alive while idle when pinned with Ctrl+T, and under low-memory conditions only unpinned sessions become eligible for shedding (automatic termination to free resources). The auto-updater has been enhanced with automatic retries on transient network failures, OS error code/category display, and current version display in the status line.
Enterprise and MCP-related fixes continue to be shipped. Issues addressed include forceLoginOrgUUID / forceLoginMethod not taking effect in third-party provider / API key sessions, MCP resources/list / prompts/list pagination dropping entries beyond the first page, a regression in Windows PowerShell for winget / Microsoft Store versions since v2.1.124, right-click / middle-click paste in GNOME Terminal, tab header display in /help and menu layout in /plugin / /status / /mobile, unknown slash commands silently failing in headless mode, and duplicate consecutive entries being recorded in prompt history. There were no new entries on Anthropic News, the Engineering Blog, or the Platform Docs Release Notes during this period, and Code w/ Claude London concluded its final day (2026-05-22).
目次 (4)
- [1] Claude Code v2.1.148 Emergency Hotfix — Bash Failure Resolved in Under Five Hours
- [2] Claude Code v2.1.147 Release — GitHub PR Inline Comments via --comment
- [What to Watch Next] Apply v2.1.148 Immediately and Evaluate --comment for CI Integration
- [Sources] Primary Source Links Covered in This Article
[1] Claude Code v2.1.148 Emergency Hotfix — Bash Failure Resolved in Under Five Hours
At 01:16 UTC on May 22, 2026 (10:16 JST), Claude Code v2.1.148 was released as an emergency hotfix (source: https://github.com/anthropics/claude-code/releases/tag/v2.1.148 ). This is a single-bug emergency fix that resolves the regression introduced in v2.1.147 the previous night, where the Bash tool returned exit code 127 (command not found) for all commands for some users.
Impact for engineer readers: ★★★
This regression was critical — affected users were effectively unable to work. Immediately after installing v2.1.147, all commands executed via the shell were observed to fail with exit 127, with no exceptions for basic commands like git, npm, or ls. Any automation driven by the Bash tool within the claude CLI — command execution from MCP, shell calls triggered by skills, chains of commands within a claude process invoked from CI — would silently break, making an immediate upgrade to v2.1.148 mandatory for affected environments.
The under-five-hour turnaround from hotfix to delivery is a prime example of the speed of release regression detection → fix → distribution. Environments with automatic updates enabled via npm or native installers should already have v2.1.148 applied, but environments with automatic updates disabled (enterprise, offline, or pinned-version deployments) must update manually. Teams that pinned v2.1.147 for rollout should prioritize either switching the pin to v2.1.148 or rolling back to v2.1.146 within 24 hours.
Note that the Claude Code Changelog (https://code.claude.com/docs/en/changelog ) is updated with each release, so check whether v2.1.148 is reflected before deciding on deployment.
| Item | Details |
|---|---|
| Release date/time | 2026-05-22 01:16 UTC / 10:16 JST |
| Type | Emergency hotfix (single bug fix) |
| Fix target | Bash tool exit code 127 regression introduced in v2.1.147 |
| Impact | All shell commands failing with exit 127 for some users |
| Action required | Immediate upgrade to v2.1.148 |
| Source | https://github.com/anthropics/claude-code/releases/tag/v2.1.148 |
[2] Claude Code v2.1.147 Release — GitHub PR Inline Comments via --comment
Claude Code v2.1.147 was released at 20:39 UTC on May 21, 2026 (05:39 JST on May 22) (sources: https://github.com/anthropics/claude-code/releases/tag/v2.1.147 , https://code.claude.com/docs/en/changelog ). This is a major release with numerous simultaneous improvements spanning session management, command system, auto-updater, and performance.
Impact for engineer readers: ★★★
The flagship new feature is the addition of the /code-review --comment option. Running /code-review --comment from the CLI causes Claude's review results to be posted directly as inline comments on a GitHub PR. The workflow of calling claude --code-review from CI to post comments on a PR becomes simpler, reducing the need to maintain a separate review bot. Effort-level specification (e.g., /code-review high) is retained, allowing depth to be adjusted based on the scale of the change. Note that the cleanup behavior previously bundled with /simplify has been removed, so any documentation or scripts still referencing the /simplify name need to be updated immediately.
On the session management front, background sessions (sessions pinned with Ctrl+T) now stay alive even when idle. Claude Code itself has been redesigned to automatically restart when necessary when applying updates, and under low-memory conditions, only unpinned sessions are eligible for shedding (automatic termination to free resources). This stabilizes workflows that involve running long-lived tasks or monitoring tasks in the background.
The auto-updater has been enhanced with automatic retries on transient network failures, OS error code/category display on failure, and current version display in the status line. In environments where distribution is intermittently blocked by an internal proxy, it was previously difficult to notice an "update failed" state, but now you can tell at a glance from the version shown in the status line. Diff rendering for large file edits has also been sped up, improving the perceived performance when working on long files.
For enterprise users, the issue where forceLoginOrgUUID / forceLoginMethod policies did not take effect in third-party provider / API key sessions has been resolved. Access control via Managed Settings now takes effect for Bedrock / Vertex sessions and direct API key sessions as well. The MCP resources/list / resources/templates/list / prompts/list pagination issue where entries beyond the first page were dropped has also been fixed, resolving the situation where large MCP servers with more than 20 resources would have entries missed.
Numerous platform-specific minor fixes have also been included (see table below).
| Change category | Details | Affected area |
|---|---|---|
/code-review --comment |
GitHub PR inline comment posting, effort level specification retained | CI review automation |
/simplify removed |
Name unified under /code-review, previous cleanup behavior deleted |
CI scripts, runbooks, team documentation |
| Session management | Background sessions (Ctrl+T pinned) remain alive when idle; only unpinned sessions shed under low memory |
Long-running operation workflows |
| Auto-updater | Automatic retry on network failure, OS error display, current version shown in status line | Internal proxy environments and team deployments |
forceLoginOrgUUID |
Now applies to third-party provider / API key sessions | Enterprise SSO control |
| MCP pagination | resources/list / templates/list / prompts/list entries beyond page 1 now retrieved |
Large MCP server integrations |
| Windows PowerShell | Regression fix for winget / Microsoft Store versions since v2.1.124 | Windows environment team deployments |
| GNOME Terminal | Right-click / middle-click paste fix | Linux business use |
| Headless mode | Unknown slash commands now surface failures visibly instead of silently failing | Script-driven execution |
/help / UI menus |
Tab header display, /plugin / /status / /mobile menu layout fixes |
CLI interaction |
| Prompt history | Duplicate consecutive entries no longer recorded | All environments |
[What to Watch Next] Apply v2.1.148 Immediately and Evaluate --comment for CI Integration
In the editorial team's view, the top priority action today is upgrading to Claude Code v2.1.148 immediately. Environments that have already installed v2.1.147 may have all Bash-based commands broken, so verify that v2.1.148 is applied on both CI systems and developer machines. Environments with automatic updates disabled should update manually, and pinned deployments should switch their pin target as a top priority.
The next item to tackle is evaluating the /code-review --comment option. The workflow of invoking claude --code-review --comment from CI to post inline comments on a PR could be a turning point for teams maintaining a separate review bot — it may be the moment to consolidate to a single CLI. Designing a branching strategy for effort levels (high / medium, etc.) at the same time will allow you to vary review depth between large and small PRs.
Additionally, the behavioral change where background sessions remain alive when idle alters the assumptions behind long-running monitoring tasks and parallel execution designs. Since the behavior of pinned sessions not being shed even under low memory is two sides of the same coin as the risk of "sessions unexpectedly persisting," it is safer to formalize Ctrl+T usage rules within your team. Code w/ Claude London concluded on 2026-05-22. We will continue to track registration trends for the Tokyo venue (2026-06-05–06), further developments on the KPMG partnership, and updates on the Stainless acquisition in this news section.
[Sources] Primary Source Links Covered in This Article
- Claude Code Releases (v2.1.148): https://github.com/anthropics/claude-code/releases/tag/v2.1.148
- Claude Code Releases (v2.1.147): https://github.com/anthropics/claude-code/releases/tag/v2.1.147
- Claude Code Releases (full list): https://github.com/anthropics/claude-code/releases
- Claude Code Changelog: https://code.claude.com/docs/en/changelog
- Anthropic News (top): https://www.anthropic.com/news
- Anthropic Engineering Blog: https://www.anthropic.com/engineering
- Platform Docs Release Notes: https://platform.claude.com/docs/en/release-notes/overview
