Claude Code CLI 2.1.148 fixes exit 127

- Anthropic’s Claude Code team said on May 22 that CLI version 2.1.148 fixed a Bash-tool regression introduced in version 2.1.147. (code.claude.com) - The changelog’s key line says 2.1.148 fixed the Bash tool “returning exit code 127 on every command for some users.” (code.claude.com) - Users can verify the patch in Claude Code’s changelog, GitHub repository, npm package history, and bundled Agent SDK releases. (code.claude.com)

Anthropic’s Claude Code team said on May 22 that CLI version 2.1.148 fixed a bug that caused the Bash tool to return exit code 127 for some users after the 2.1.147 release. The fix appears in the official Claude Code changelog and in the project’s public GitHub repository. (code.claude.com) Anthropic described it as a regression introduced in 2.1.147, then corrected in the next release. Social posts around the issue focused on breakage, patches and temporary workarounds, but the clearest public record is the changelog entry itself. ### What exactly was fixed in 2.1.148? Version 2.1.148 says the release “Fixed the Bash tool returning exit code 127 on every command for some users,” according to Anthropic’s changelog. The same line adds that the problem was “a regression introduced in 2.1.147.” Exit code 127 is the standard shell code for “command not found.” LinuxConfig, in a general explanation of Bash return codes, says 127 usually means the shell could not locate the command being executed. (code.claude.com) ### Why did users care about an exit-127 bug? Claude Code is Anthropic’s terminal-based coding tool, and its Bash tool is part of how the product runs shell commands inside coding workflows. When that path fails, basic command execution can break. Anthropic’s npm package page describes Claude Code as a tool that helps users code faster by executing routine tasks, explaining code and handling git workflows through natural-language commands. (code.claude.com) The changelog wording matters because it says the Bash tool was returning exit code 127 “on every command” for affected users. (linuxconfig.org) That suggests the regression hit a core path rather than a narrow edge case, though Anthropic limited the scope by saying it affected “some users.” That is an inference from the release note wording, not a broader company statement. ### Where does 2.1.147 fit in the sequence? The public changelog shows 2.1.147 immediately before 2.1.148. The diff view of the changelog also shows the 2.1.148 bug-fix note directly above the 2.1.147 feature list, linking the fix to the prior release in Anthropic’s own release history. (npmjs.com) By May 24, the release train had already moved on. Anthropic’s changelog page lists later versions including 2.1.149 and 2.1.150, indicating 2.1.148 was a quick corrective release rather than a long-lived current version. (code.claude.com) ### How can users verify they have the fixed build? Anthropic’s documentation says users can run `claude --version` to check the installed version. The official changelog page is generated from the project’s `CHANGELOG.md` on GitHub, giving users two primary places to confirm the fix text. (github.com) The npm registry also shows Claude Code package versions, and Anthropic’s Python Agent SDK release page shows bundled CLI updates. One SDK release published yesterday updated the bundled Claude CLI to version 2.1.148, after the prior SDK release had bundled 2.1.147. (code.claude.com) ### What should users watch next? As of May 24, Anthropic’s public changelog lists versions newer than 2.1.148, including 2.1.149 and 2.1.150. Users tracking this issue can check the Claude Code changelog, the GitHub `CHANGELOG.md`, and package-release pages to see whether later releases mention related Bash, shell or permission fixes. (code.claude.com) (npmjs.com)

Get your own daily briefing

Scout delivers personalized news, insights, and conversations tailored to your role and industry.

Download on the App Store

Shared from Scout - Be the smartest in the room.