Sessions

A session in Deputy Shell is an independent terminal: its own process, its own input and output, and its own retained history. You can run several sessions at once without their output mixing together, and a Codex session is simply a normal terminal session running the codex command — it has no special isolation of its own.

Session states

• Running — the terminal process is live.
• Stopped — you (or "Stop All") ended the live process, but the session record, its workspace, and its recent output remain.
• Needs resume — the process disappeared unexpectedly (for example, after the app or device restarted) and needs to be started again to continue.
• Crashed — the process exited on its own, unexpectedly.

Deleting a session is a separate, further step from stopping one — see Managing Sessions for the distinction.

What's retained across restarts

Deputy Shell stores up to approximately 1 MB of recent terminal context per session. When that limit is exceeded, older content is trimmed and the newest portion is retained. This is a bounded recent-context buffer, not a complete or unlimited terminal transcript — and it's excluded from backups, diagnostics exports, and workspace exports. Deleting a session removes this retained context permanently.