Remote and hosted sessions stop when the server accepts nothing from them

What

When 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.

• The worker now tracks how long it has gone with no heartbeat or upload accepted, using stopWhenNothingAccepted and nothingAcceptedSinceMs.
• Once a time limit is reached, it logs a message beginning "CCR has accepted no heartbeat or upload from this worker for" and stops.
• A 429 response, meaning too many requests, resets that count instead of adding to it.
• Hosted sessions get an onNothingAccepted callback that ends the session with the kind "nothing-accepted".

Why

A 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.