Cloud session: coming back after a restart

A supervised cloud session keeps running on its box when the desktop closes. This page explains what you should see when the app comes back, and what the app does about it.

What happens at the next start

The app asks the controller what your session's own worker is doing, and takes one of three roads:

The controller says	What the app does
your worker still holds its grant (current)	attaches to the live run and replays what you missed — nothing is launched, nothing is charged twice
your worker's grant expired, but the controller still lists the session	re-drives the session, exactly as before
anything else — a released grant, a box that cannot be read	today's behaviour, unchanged

An attach is a relay: it writes no prompt and asks for no new worker, so it is the one action that can never collide with the run already on the box. That collision — a fresh launch refused with "predecessor not released" — is what used to end such a session in error with your message undelivered.

What you see

• The run's missing output, including its final message, is replayed into the transcript from the point you last saw it — as if you had never closed the app.
• The session's card follows the run's real state; it stops saying "working on the cloud machine" once the run has finished.

Sending a message while the run is still working

Your message is queued behind that run rather than starting a rival turn, and the app attaches the relay so it sees the moment the run ends. The message is then delivered once — the ordinary way, with its attachments — when the run is finished.

When the session is not recovered this way

• A session that never ran under the supervisor has no replay position, so it keeps the old behaviour.
• A box you stopped yourself is never re-entered: a parked box stays parked.
• A session left needs you + suspended by a clean quit belongs to the suspended door, which already reattaches and replays.

Related

• Cloud session: when it won't start
• Cloud session state