{"version":"2.1.323","anchor":"headless-stream-position-retry-backoff","canonical_anchor":"headless-stream-position-retry-backoff","heading":"Cloud sessions retry longer when reading their stream position","tier":"notice","area":"Cloud Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/headless-stream-position-retry-backoff","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Cloud sessions retry longer when reading their stream position\n\nHeadless cloud sessions now retry reading their stream position after 0.5, 2 and 4 seconds instead of retrying once\n\n**What**\n\nIn headless cloud sessions, which run on a remote machine with no screen, Claude Code reads a stream position to know where it is in the session's output. When that read fails, Claude Code now tries again after waits of 0.5, 2 and 4 seconds, all within an overall time limit. Before, it retried only once.\n\n**Why**\n\nRemote sessions are more likely to get through a short hiccup instead of failing.\n\n- Area: Cloud Sessions\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}