EVERYDAY · SHELL

Continue one shell from different devices.

A shell is an interactive terminal retained by the remote host. Devices enter and render it; they do not determine whether it remains alive.

Lifecycle

Creating a shell creates a server-side Terminal that owns the PTY, process, and authoritative terminal state. Closing a client window removes its Attachment; it does not automatically terminate the Terminal.

Create Terminal→Attach device→Disconnect→Attach again

Disconnect and resume

When a connection recovers, the client finds the still-running Terminal by canonical UUID and receives its current state. With input_resume v2, the server validates recovery credentials held in this device’s Keychain. Missing, expired or unavailable credentials leave automatic recovery read-only until explicit takeover. The recovery identity is not synchronized through iCloud, and seamless network migration is not guaranteed.

Multiple devices

A computer and phone can enter the same shell and see the same server-authoritative state. One Controller owns input and resize at a time; other Attachments remain visible as Viewers and can safely take over when needed.

Restart boundaries

Managed worker reuse requires a compatible internal protocol. Cross-version worker upgrades require cold maintenance; live PTY migration is not implemented.

Client exit or network loss: the Terminal keeps running.
Managed gateway restart: an existing user worker can keep the Terminal.
User-worker or full-server restart: running Terminals are not currently restored from disk.