Code execution

Use bead exec for code execution on an existing Linux machine. Commands use /bin/sh -c and start in /root unless you set --cwd.

Run shell commands in a cloud VM

Replace ID with your machine ID:

bead exec ID 'uname -a'
bead exec ID 'mkdir -p /root/project'
bead exec ID 'pwd && ls -la' --cwd /root/project

The working directory must exist. Shell quoting happens first on your computer, then in the guest. Single quotes keep guest variables such as $HOME from expanding locally.

Capture exit codes from remote commands

bead --json exec ID 'printf "hello\n"; exit 7'

JSON output includes exit_code, stdout, and stderr. A nonzero exit code means the command failed even when the transport succeeded. Plain CLI output prints complete stdout and stderr. The CLI exits 0 for remote success and 1 for a nonzero remote exit; use JSON exit_code to read the remote status, or bead run to preserve it as the local exit status. The CLI exec transport sets a 25-second execution deadline. Use bead run for a bounded build with a longer command timeout, or runner turns for coding-agent work.

Use MCP

The hosted bead:sandbox_exec tool uses the same guest transport. Inspect its exit_code and retained output fields. Read output and recovery before retrying after an uncertain response.

Transfer files, forward an application port, or pause the machine.

Get started

Use cases

Connect

Run work

Set up machines and templates

Snapshots and fork

Machines

Agents and computer use

Worktrees

Fleets and swarms

Teams and organizations

Security and data

Help

Code execution

Run shell commands in a cloud VM

Capture exit codes from remote commands

Use MCP

Next

​Run shell commands in a cloud VM

​Capture exit codes from remote commands

​Use MCP

​Next

Run shell commands in a cloud VM

Capture exit codes from remote commands

Use MCP

Next