You'll notice
Useful2 Signal2
Cloud sessions now report a clean exit right away instead of leaving the server to notice missed heartbeats.
What's wrong with this entry?
Anonymous. No account, no email.
What
When a remote worker session shuts down it now tells the server it is going, by sending a /worker update with connection_status: "disconnected" and the current worker generation number. Nothing gates this, so on a cloud or remote session in this build a clean exit is reported immediately rather than being inferred from missed heartbeats.
Details
- Skipped while a turn is still running, recorded as
cli_worker_goodbye_skipped_mid_turn. - Skipped entirely when the caller passes
{ goodbye: !1 }, which the internal rewire and reconnect paths do, so a reconnect does not look like a disconnect. - Successful sends are recorded as
ccr_worker_goodbye. - The bridge teardown waits on a flush accessor before exiting, so the process does not die before the update lands.
Evidence
cli_worker_goodbye_skipped_mid_turn
Strings lifted out of the shipped bundle, so the claim above can be checked against them.