Create a new Runloop Devbox.

List devboxes on the account.

Retrieve details for a single devbox by id.

Update a devbox's name and/or metadata.

Suspend a devbox, preserving its disk state.

In-memory state (running processes, env vars) is lost; restart background processes after resuming.

Resume a suspended devbox.

Shut down (delete) a devbox and release its resources.

Execute a command on a devbox and block until it completes.

Each call spawns an isolated shell by default - env vars and CWD do not persist between calls. Pass the same shell_name to reuse a stateful named shell session.

Start a command on a devbox and return immediately.

Use this for long-running or background processes (servers, watchers). The returned execution_id can be polled later.

Create or overwrite a file on a devbox.

Use this to write new files or edit existing ones (the full contents are written atomically).

Read the contents of a file on a devbox.

Create a disk snapshot of a devbox's current state.

Snapshots persist and accrue storage charges until explicitly deleted. A new devbox can later be created from the snapshot via snapshot_id.

List disk snapshots, optionally filtered to a devbox.

Create or reconnect to an interactive PTY session on a devbox.

Reusing the same session_name reconnects to the same logical PTY session while it is still alive. The returned connect_url is the WebSocket endpoint used by pty_send_command.

Send a command to an interactive PTY session and capture its output.

Creates the session if it does not exist (or reconnects if it does), opens the WebSocket data plane, writes the command, and reads output until the terminal is quiet for idle_timeout seconds (or max_wait elapses).

Prefer execute_command for non-interactive commands; use this for TTY-aware programs (REPLs, TUIs, interactive shells).

Control an existing PTY session: resize, signal, or close.