Skip to main content

Sandbox Sessions

Spin up isolated environments where AI agents can build software with full permissions.

Quick Start

Commands

runtm start

Start a new sandbox session. Shows an interactive menu to select mode and agent.
Options:

runtm prompt

Send a prompt to the agent in autopilot mode.
Options:

runtm attach

Attach to an existing sandbox shell.
When attached, you’ll see a custom prompt indicating you’re in a sandbox:
Type exit to leave. The session persists and you can reattach later.

runtm session list

List all sandbox sessions.
Output shows:
  • Session ID
  • Status (running/stopped)
  • Mode (autopilot/interactive)
  • Created time
  • Initial prompt
Active session is marked with *.

runtm session stop

Stop a sandbox without deleting files.

runtm session destroy

Permanently delete a sandbox and its workspace.

runtm session deploy

Deploy the code from a sandbox to a live URL.

Modes

Autopilot Mode

The agent runs autonomously. You control it via runtm prompt:
Best for:
  • Automated workflows
  • CI/CD pipelines
  • Hands-off development

Interactive Mode

You drop into the sandbox shell and control the agent manually:
Best for:
  • Learning and exploration
  • Debugging
  • Fine-grained control

Environment Variables

Inside the sandbox, these variables are set:

Terminal Tracking

Each terminal tracks its own active session. This means you can:
  • Have multiple terminals with different sandboxes
  • Run runtm attach in each terminal to reconnect to that terminal’s sandbox
  • runtm prompt targets the active session in the current terminal

Requirements

For full OS-level isolation, install:
Without these, sandboxes still work but run without isolation (with a warning).