Claude Code v2.1.229 Changelog

This update is all about making Claude Code more reliable and less frustrating to use, especially if you run it in complex setups like cloud servers or inside your code editor. It matters most to developers and power users who use Claude to write code, manage plugins, or automate their workflow, giving them a smoother, faster, and safer experience.

What's new

• Remote Control resume: You can now easily pick up right where you left off in a remote session using claude remote-control --continue.
• Server hooks for self-hosted setups: If you run Claude on your own servers, you can now use "hooks" (custom automated triggers) just like you can in managed cloud environments.
• Plugin marketplace commands: Plugins can now be loaded directly from a local command (like from your code editor). You don't even need to restart Claude to apply them.
• Better session labels: When looking at your active agents, disconnected remote sessions are clearly marked as offline, and cloud sessions are labeled cloud so you know exactly what you're looking at.
• VSCode session groups: In the VSCode extension sidebar, you can now group your chats. You can right-click to create, rename, or delete groups, and click multiple chats at once to move them around.

Improvements

• Smoother long thinking: When Claude takes a while to "think" through a complex problem, it now sends background signals to keep the connection alive. This stops cloud platforms (like Vertex or Bedrock) from timing out and disconnecting.
• Faster workflow fan-outs: When Claude splits a big task into smaller parallel tasks, it now staggers them slightly. This lets the later tasks reuse cached information from the earlier ones, saving time and computing power.
• Clearer error messages: If your prompt is too long, Claude now explains exactly why it couldn't automatically shrink it down, instead of just telling you to run /compact.
• Safer git commands: The /commit-push-pr tool will no longer auto-approve risky git commands (like --force or --no-verify). You now have to manually approve them to prevent accidental mistakes.
• Better sandbox security: Network security rules are now stricter to prevent loopholes, and a tool called /doctor will warn you if your settings are ambiguous.
• Login warnings: If you're using a custom override token to log in, Claude will remind you of this after you successfully sign in, so you don't forget your setup.
• Resizable side panels: In VSCode, the panel where you ask side questions (/btw) can now be resized by dragging its edge.
• VSCode feedback: The "Report a problem" button now opens the actual built-in feedback tool instead of an old, broken survey link.

Fixes

• Disappearing text: Fixed an issue where long responses would partially vanish while streaming and then print twice in the terminal.
• Tool call crashes: Fixed a crash that happened if a tool tried to use a number instead of text for things like file paths or commands.
• Narrow window crashes: Fixed a crash that happened if you squeezed your terminal window too narrow while a progress bar or table was trying to render.
• Windows file path crashes: Fixed a crash on Windows when tools tried to read files using extra-long or network folder paths.
• Auto mode failures: Fixed an error that broke "auto mode" for users who turned off a specific background header in their settings.
• Model switching: Fixed an issue where claude.ai subscribers using a custom network gateway couldn't switch to certain Sonnet or Opus models.
• Login redirects: Fixed an issue where strict security servers would reject logins because Claude was using localhost instead of 127.0.0.1 in its web links.
• Stuck spinners: Fixed a bug where the loading spinner would freeze forever if you typed a slash command (like /help) in your laptop terminal during a remote session.
• Missing GitHub reviews: Fixed a problem where the GitHub app would finish a code review but forget to actually post the review on the pull request.
• UI freezing in IDEs: Fixed multi-second freezes that happened when editing a file that had thousands of error warnings from your code editor.
• Leftover plugin files: Fixed one-off plugin commands that left behind "liveness" files, which were blocking old plugins from being cleaned up.
• CPU limit bugs: Fixed an issue where workflows inside limited containers (like Docker) would try to use the whole computer's CPU power instead of respecting the container's limits.
• File watcher leaks: Fixed a memory leak that happened when files were replaced, and fixed a crash on Windows when watching network or virtual drives.
• Blank message errors: Fixed a 400 API error that happened if you accidentally sent a message