Stop and resume
Stop a session and its box uses no CPU or memory. The conversation, the files, the installed packages, the VS Code settings, everything in the container is kept. Resume brings it back where it was and the agent reloads the conversation, so you continue as if nothing happened.
Things you can do with it
Park a project for a week
Stop the session on Friday. On Monday, Resume, and the agent still knows what it was doing and the dev server's dependencies are still installed.
Keep ten sessions without ten machines' worth of RAM
Only running boxes take memory. Stop the ones you are not looking at and start them again when you need them.
Let scheduled runs clean up after themselves
A nightly task can start a session from a template and stop it when the turn ends; the transcript stays and you can resume it if the result needs a follow-up.
Resume from the phone
A stopped session shows Resume in its header. Sending a queued message to it resumes it first.
How it works
Stop pauses the Docker container; the filesystem and the agent's own records stay in it. Resume starts it again, reconnects terminals and the Code pane and restarts the agent process, which reloads the conversation. Delete removes the session, its container and its snapshots for good; forks started from it keep working.
Compared with other products
| Sessionboxer | Devin | Cursor Cloud Agents | Codex cloud | Claude Code on the web | OpenHands | T3 Code | |
|---|---|---|---|---|---|---|---|
| Stop a session and resume it with the machine intact | ✓ | ✓ | — | — | — | — | n/a |
| Isolated sandbox per session | Docker, or a Windows/macOS VM | VM | VM | container | VM | Docker | ✗ (your machine) |
| Runs on your machine or your server | ✓ | ✗ | ✗ | ✗ | ✗ | ✓ | ✓ |
Devin sessions sleep when idle and wake when you message them, with the machine kept. Cursor Cloud Agents, Codex cloud and Claude Code on the web treat a task as finished once the agent stops; follow-ups start the agent again in the environment, but the docs do not describe pausing and resuming a machine. On your own hardware, OpenHands conversations can be reopened; T3 Code has no machine to pause.
Based on each product's public documentation, September 2026; ✓ = offered, ✗ = not offered, — = not found in the docs. Corrections welcome as an issue.