Claude Code 2.1.252

On some Macs, Bash commands would suddenly fail with task output swap refused (tasks dir moved or linked). The sticking point was the tasks directory where command output is parked: if that directory had been moved, or replaced with a link pointing somewhere else, Claude no longer recognized the spot, refused to swap the finished output back in, and the whole command went down with it. That case is now fixed, so the command runs to the end whether the directory moved house or turned into a link.

You hit "always allow" in a fresh project to stop being asked the same thing every time, and the very next time you do that action, the same prompt shows up again. The decision has to be written into the project's .claude/settings.local.json, and when the project does not have that file yet, your choice had nowhere to land, so clicking it changed nothing. Now "always allow" sticks even in a project without that file, and the same question stays away.

Remote Control sessions hosted by Claude Desktop or VS Code ran into the same thing: when the connection to claude.ai was degraded, a tool had actually finished, yet the session sat still for minutes before anything moved. The news of completion never made it back, so you waited without knowing whether it was still working or had died. That stall is now fixed, and on a shaky connection the session reacts as soon as the tool ends.

When a background task fails, the error output is sent back into the conversation for you to read. Some failures produce a staggering amount of it; git errors on a full disk are one example. Once such a notification was packed into the conversation, the whole thing went past the API request size limit, the ceiling on how much data can be sent in one go, and the conversation was stuck there. Very large failure output no longer bursts the request, so a failed task still notifies you and the conversation keeps going.