{"version":"2.1.293","anchor":"rate-limited-interrupted-turn-auto-resume-can-yield-to-a-wai","canonical_anchor":"rate-limited-interrupted-turn-auto-resume-can-yield-to-a-wai","heading":"Cloud sessions can let your waiting message go first after a rate-limited turn","tier":"notice","area":"Cloud Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293\/e\/rate-limited-interrupted-turn-auto-resume-can-yield-to-a-wai","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293","markdown":"### Cloud sessions can let your waiting message go first after a rate-limited turn\n\nIn 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\n\n**Unclear.** What the remote switch falls back to when the server sends nothing is not known.\n\n**What**\n\nA 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.\n\nNow, when all of these hold, Claude Code skips that automatic resume:\n\n- Claude Code is running as a remote session (`CLAUDE_CODE_REMOTE` is set)\n\n- The interrupted turn ended because of a rate limit (the service refusing more requests for a while)\n\n- A message from you is already waiting in the queue\n\n- A remote setting that Claude Code checks is switched on\n\nIn that case your waiting message is handled instead of the old turn being retried.\n\n**Why**\n\nIn cloud sessions, a rate-limited turn being resumed could hold up a new message you had already sent. This lets your message go first.\n\n- Area: Cloud Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}