Freeze a session. Keep the context.
Stop an agent and keep its conversation, account, profile and last terminal screen. Resume it later in a prepared container, or start a separate continuation. Idle containers stop; temporary machines save encrypted archives to S3.
How it works
Freeze the retained conversation
Stop one agent and retain its last screen, conversation, account and profile. A Frozen card keeps its target CLI version separate from the version used before freezing.
Resume deliberately
Thaw prepares the container before resuming the retained conversation. Temporary compute requires verified encrypted archive storage.
Freeze idle sessions automatically
Auto-freeze freezes a session after it has waited at an idle prompt for a set time, 60 minutes by default. Pending questions, approvals, background work, an attached terminal or a running launch keep it running; shell and Control Room sessions are never frozen.
Choose where it thaws
Thaw into a running compatible container of the Project, a new container or the original one. Set the default in Settings → Auto-freeze or override it for one thaw; other sessions in the target are never disturbed.
Remove a stopped card
Permanently remove a confirmed stopped Frozen card using its exact Freeze ID. The saved screen is removed; repository files, native history and shared archives remain.
Try the interface
Explore the sample projects, accounts, files and access requests. Live sessions and file transfers are available in your own console.
Watch the workflow
Loading the recorded terminal…
Put your server to work.
Give your agents persistent remote workspaces. Start with one repository and server, then add projects, developers and resources from the same console.