Claude Code v2.1.252 ships four small-but-nice bug fixes!
Hi, I'm Shii-chan! Today's news isn't flashy, but it's the kind of thing that quietly makes life better if you use Claude Code every day.
Claude Code ReleaseWhat was announced?
According to the Claude Code release notes on GitHub, v2.1.252 is out with four bug fixes.
- Fixed Bash commands failing with "task output swap refused (tasks dir moved or linked)" on some Macs
- Fixed "always allow" not saving in a project that has no
.claude/settings.local.jsonyet - Fixed Remote Control sessions hosted by Claude Desktop or VS Code stalling for minutes after a tool finished when the connection to claude.ai was degraded
- Fixed background task notifications with very large failure output (for example git errors on a full disk) making the conversation exceed the API request size limit
Why it matters
None of these are new features, just quiet bug fixes, but they're exactly the kind of small friction that adds up if you use Claude Code every day. A command failing with a cryptic error, a permission setting that silently doesn't save, a remote session that freezes, or a conversation breaking just because a failure log was too big — each of these can throw off your flow. Steady reliability fixes like these matter even when they don't make headlines.
What changes
If you were hitting any of these specific situations, here's what should be better now.
- Bash commands on affected Macs should no longer fail with that swap-refused error
- "Always allow" settings should now save correctly even in brand-new projects
- Remote Control sessions should be less likely to stall for a long time when the connection is degraded
- Background task notifications with large failure output should be less likely to break the conversation
Dive Deep
Here's a bit more detail on what each fix addresses, based on the release notes.
- Bash command failures: On some Macs, the task output swap process was being refused because the tasks directory had been moved or linked, which caused commands to fail. This release addresses that refusal case.
- settings.local.json issue: In a new project without an existing
.claude/settings.local.jsonfile, choosing "always allow" wasn't being saved. This looks like a gap in handling the case where the file doesn't exist yet. - Remote Control stalling: Remote Control sessions hosted by Claude Desktop or VS Code could stall for minutes after a tool finished running when the connection to claude.ai was degraded. That's now fixed.
- API request size limit from large failure output: When a background task produced a very large failure output — such as git errors from a full disk — the resulting notification could push the conversation over the API's request size limit. This has been fixed.
Wrap-up
- Fixed a Bash command failure affecting some Macs
- Fixed "always allow" not saving in projects without an existing settings.local.json
- Fixed Remote Control sessions stalling for minutes under degraded connections
- Fixed conversations exceeding the API request size limit due to large failure output
No new features here, but if you use Claude Code heavily every day, this is the kind of release where you might quietly recognize a few bugs you've personally run into.