Claude Code 2.1.293 reverts a cloud-session fix that shipped two days earlier
Claude Code 2.1.293 takes back a fix that version 2.1.290 shipped two days earlier, and it says so without euphemism. Anthropic’s changelog for 2.1.293 reads: “Reverted the 2.1.290 fix for cloud sessions staying asleep after a container restart lost a pending /loop wakeup or scheduled task; Claude is no longer told, and the session stays asleep.”

Claude Code running a long job in a terminal. Scheduled tasks and cloud sessions are what the reverted fix touched. Image: Anthropic
Two days earlier, 2.1.290 had claimed the opposite ending: “Fixed cloud sessions staying asleep after a container restart lost a pending /loop wakeup or scheduled task; Claude is now told and can schedule it again.” The behaviour is back where it started. The npm registry puts 2.1.290 at 18:12 UTC on October 5 and 2.1.293 at 17:18 UTC on October 7, so the fix lasted one day and 23 hours.
The release in between existed to clean up after it
Between the two sits 2.1.291, published at 03:32 UTC on October 6, nine hours and 19 minutes after 2.1.290. It shipped two fixes and nothing else, both of them regression fixes: “Fixed a regression in 2.1.290 where cloud sessions could drop answers to permission prompts” and “Fixed a regression in 2.1.288 where the last messages of a session could be lost when quitting”.
The sequence runs fix on October 5, emergency patch on October 6, revert on October 7. For anyone running Claude Code in a cloud session with a scheduled task, that is three builds in three days to arrive back at the original behaviour, with a permission-prompt bug visible for nine hours in the middle.
Anthropic published 2.1.288 on October 2 and 2.1.293 on October 7, six releases in under five days. At that cadence a fix and its reversal can pass through an installation inside a single working week without anyone noticing either event. Two of the six changed behaviour users had to know about: 2.1.289 closed a second route past the rm guard on October 3, and 2.1.292 switched stdio MCP servers to a newer protocol on October 6.
A second revert reaches back a fortnight
The same release undoes something older. “Reverted the auto mode denial message change from 2.1.281 that told Claude a denial covers the outcome, not only the exact command”, the entry says. Version 2.1.281 went to npm at 17:01 UTC on September 23, so that wording survived 14 days before being pulled. Auto mode is the setting that lets Claude Code run commands without asking each time, and the reverted change governed how it read a refusal.
Two reverts are not the whole release. 2.1.293 also adds Claude Haiku 5.5, “now the default Haiku model on the Anthropic API”, alongside dozens of fixes. One of them closes “a memory leak where an HTTP MCP connection kept every request it had sent until it closed”, which a long-lived session would feel before a short one. Another “Changed claude.ai skill syncing to check for changes about every 40 minutes, instead of every 10, while no session is in use”, cutting idle polling by three quarters.
The separate stable release channel still points at 2.1.285, published on September 29. Version numbers were read from the npm registry at 22:05 UTC on October 7.
Anthropic does not say why the cloud-session fix went back out, and nothing in the release notes describes lost work. The week it does describe runs in four steps: a problem identified, a fix written, a regression caught, and the fix withdrawn, each of them written down rather than quietly dropped.