TL;DR
Update past 2.1.147 now. The Bash tool returns exit code 127 on every command in 2.1.147 (a regression); 2.1.148 ships the fix same-day.
/simplifyis gone, replaced by/code-review. The old cleanup-and-fix behavior is removed;/code-reviewreports correctness bugs at a chosen effort level, and--commentposts findings as inline GitHub PR comments (more below).Pin background sessions with Ctrl+T in
claude agents. Pinned sessions stay alive when idle, restart in place for Claude Code updates, and are only shed under memory pressure after non-pinned sessions.
New in 2.1.148, 2.1.147
2.1.148 (May 22, 2026)
- Fixed the Bash tool returning exit code 127 on every command for some users (a regression introduced in 2.1.147)
2.1.147 (May 22, 2026)
- Pinned background sessions (
Ctrl+Tinclaude agents) now stay alive when idle, are restarted in place to apply Claude Code updates, and are shed under memory pressure only after non-pinned sessions - Renamed
/simplifyto/code-review. It now reports correctness bugs at a chosen effort level (e.g.,/code-review high); pass--commentto post findings as inline GitHub PR comments. The old cleanup-and-fix behavior has been removed - Improved auto-updater: retries transient network failures, reports specific error categories and OS error codes on failure, and shows the current version when an update fails
- Improved diff rendering performance for large file edits
- Prompt history no longer records consecutive duplicate entries
- Fixed enterprise login restrictions not being enforced against third-party-provider and API-key sessions
- Fixed
&in!command output displaying as& - Fixed unknown slash commands silently doing nothing in headless/SDK mode
- Fixed
/helprendering a broken tab header on small terminals - Fixed shell snapshot dropping user functions whose names start with a single underscore
- Fixed plugin agents dropping all but the last Agent type entry
- Fixed hook
ifconditions likePowerShell(git push*)never matching - Fixed PowerShell tool dropping output for commands that rely on the default formatter
- Fixed: on Windows, "Yes, and don't ask again" for PowerShell scripts now writes a matching rule
- Fixed PowerShell tool failing on Windows when
pwshis installed via winget or the Microsoft Store - Fixed
/effortopening with the slider on the wrong level - Fixed paginating MCP servers dropping resources, templates, and prompts past page 1
- Fixed full-screen strobing in attached background sessions on Windows Terminal
- Fixed: on Windows, removing a background-job worktree no longer follows NTFS junctions into the main repo
- Fixed
/backgroundrefusing sessions whose only typed input was a skill or custom slash command - Fixed auto mode suppressing
AskUserQuestionwhen the user or a skill explicitly relies on it - Fixed
/themecolor editor dialogs not responding to Esc - Fixed an uncaught exception at the end of streaming sessions when running via the Agent SDK
- Fixed a rare hang when waiting for scroll to settle on Windows
- Fixed stale and doubled rows in the agent view list on Windows with CJK characters
- Fixed pasted text being delivered to agents as an unreadable placeholder
- Fixed plugin component counts being doubled when manifest paths overlap default directories
- Fixed backgrounded sessions re-prompting for tool permissions already granted
- Fixed GNOME Terminal right-click and middle-click paste not inserting text
- Fixed
CLAUDE_CODE_SUBAGENT_MODELnot applying to teammate processes - Fixed slash commands followed by a tab or newline being treated as unknown
- Fixed spacing and layout glitches in several menus
- Fixed stripped images prompting repeated re-reads of absent media
Notes
/simplify to /code-review is a break, not just a rename
2.1.146 introduced the /simplify to /code-review rename. 2.1.147 completes the transition by removing the old cleanup-and-fix behavior entirely. /code-review is now a pure reporting tool: it finds correctness bugs at the effort level you choose and, with --comment, writes them directly as inline PR comments. If you had /simplify in any scripts, hooks, or muscle memory, the command still works under the new name but does something fundamentally different.
Bash exit code 127: a same-day hotfix
2.1.147 introduced a regression where the Bash tool returned exit code 127 on every command for some users. 2.1.148 shipped the same day to fix it. If you auto-updated to 2.1.147 and noticed broken shell commands, that was the cause. The turnaround is notable: this is one of the fastest regression-to-fix cycles in the changelog.