v0.2.26 or later.
Install and authenticate
Install or upgrade the LangSmith CLI:--format pretty to list commands for human-readable tables:
End-to-end workflow
Create a sandbox, then run commands inside it:Manage snapshots
Build snapshots from Docker images:--registry-id:
Manage sandboxes
Create a sandbox with the default runtime. Add--snapshot-id only when you want to boot from a reusable custom snapshot:
Proxy configuration
Use--proxy-config @proxy.json on create or update to configure the sandbox auth proxy. Prefer workspace secrets for credential injection instead of placing raw secrets in local files.
Run commands
Usesandbox exec for one-off commands:
-- is sent to the sandbox as the command. The CLI prints stdout to stdout, stderr to stderr, and exits with the sandbox command’s exit code.
Open an interactive console
Usesandbox console for a PTY-backed interactive shell:
--forward-ssh-agent requires SSH_AUTH_SOCK to be set locally. Interactive console sessions are not supported on Windows; use SSH access instead.
Tunnel TCP ports
Usesandbox tunnel when you need a local TCP port that forwards to a service listening inside the sandbox. This is useful for databases, language servers, custom protocols, or local tools that expect localhost.
Start a service in the sandbox, then tunnel to it:
--local-port, the CLI uses the same value as --remote-port:
Ctrl+C.
You can also tunnel by sandbox URL instead of name:
Set up SSH access
Usesandbox ssh-setup to configure standard SSH tools such as ssh, scp, rsync, and sftp through a sandbox tunnel.
Host sandbox-<name> block to ~/.ssh/config, and writes sandbox host keys to ~/.ssh/known_hosts_sandboxes.
After setup, connect with:
sshd on port 22. If sshd is not running, ssh-setup warns and the SSH connection will not work until you start it inside the sandbox.
Command reference
Connect these docs to Claude, VSCode, and more via MCP for real-time answers.

