{"version":"2.1.323","anchor":"worker-stops-itself-when-ccr-accepts-nothing-from-it","canonical_anchor":"worker-stops-itself-when-ccr-accepts-nothing-from-it","heading":"Remote and hosted sessions stop when the server accepts nothing from them","tier":"notice","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/worker-stops-itself-when-ccr-accepts-nothing-from-it","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Remote and hosted sessions stop when the server accepts nothing from them\n\nA remote worker now stops itself after the server has accepted none of its heartbeats or uploads for a set time\n\n**Unclear.** Whether this stop is switched on, and after how long, depends on a value the host supplies that is not stated.\n\n**What**\n\nWhen Claude Code runs as a remote worker, a copy running on a server for a hosted or cloud session, it regularly sends heartbeats (\"still here\" signals) and uploads to the service, called CCR.\n\n- The worker now tracks how long it has gone with no heartbeat or upload accepted, using `stopWhenNothingAccepted` and `nothingAcceptedSinceMs`.\n\n- Once a time limit is reached, it logs a message beginning \"CCR has accepted no heartbeat or upload from this worker for\" and stops.\n\n- A 429 response, meaning too many requests, resets that count instead of adding to it.\n\n- Hosted sessions get an `onNothingAccepted` callback that ends the session with the kind \"nothing-accepted\".\n\n**Why**\n\nA remote worker the service has stopped listening to now exits on its own instead of running indefinitely. A session that ends this way will show \"nothing-accepted\" as the reason.\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}