Follow Discord
Sweep 08 Oct 2026 · 18:53Z Build v2.1.295 516 read Stable v2.1.286 Latest v2.1.295 Next v2.1.295 Feeds RSS JSON llms.txt llms-full.txt Unofficial
HomeReleasesv2.1.293entry #88

Claude Code v2.1.293 ·

Cloud sessions can let your waiting message go first after a rate-limited turn

In remote sessions, a turn cut off by a rate limit is no longer auto-resumed ahead of a message you have already queued, when a remote switch is on

You'll notice Improvements
JSON All of v2.1.293
You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
Cloud SessionsArea: what it touches
ImprovementsKind: in v2.1.293,
ImprovementsSection of the release

Unclear What the remote switch falls back to when the server sends nothing is not known.

What

A turn is one round of Claude working on your request. When a turn is interrupted, Claude Code normally picks it back up automatically. Before, it always did so.

Now, when all of these hold, Claude Code skips that automatic resume:

  • Claude Code is running as a remote session (CLAUDE_CODE_REMOTE is set)
  • The interrupted turn ended because of a rate limit (the service refusing more requests for a while)
  • A message from you is already waiting in the queue
  • A remote setting that Claude Code checks is switched on

In that case your waiting message is handled instead of the old turn being retried.

Why

In cloud sessions, a rate-limited turn being resumed could hold up a new message you had already sent. This lets your message go first.

How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtWhat the remote switch falls back to when the server sends nothing is not known.

See this entry in the whole of v2.1.293 →

Feedback