Run commands, capture and stream output, and start, manage, and signal background processes
Run shell commands inside sandboxes with full stdout/stderr capture, real-time streaming, and configurable timeouts — then keep long-running services alive with background processes, signals, stdin, and supervised restarts.Commands and processes share one API. Use run / exec when you want to run something and wait for the result; use start_process when you want to start something that keeps running and manage its lifecycle.
Sandbox-specific operations use sandbox-specific ingress, commonly seen as https://<sandbox-id-or-name>.sandbox.tensorlake.ai, derived from the sandbox’s ingress_endpoint.For named sandboxes, you can use the sandbox name in place of the ID — both in the proxy hostname and in CLI/API commands. For example, https://my-env.sandbox.tensorlake.ai/api/v1/processes and tl sbx exec my-env python main.py work the same as their ID-based equivalents. The proxy resolves the name to the underlying sandbox automatically.The command and process APIs documented here run on the management URL on port 9501, which always requires authentication. Unauthenticated proxy access applies only to exposed user ports.
# Run in an existing sandbox — use the sandbox ID or nametl sbx exec my-env python -c 'print("Hello from sandbox!")'# Or create, run, and tear down in one steptl sbx run python -c 'print("Hello from sandbox!")'
from tensorlake.sandbox import Sandboxsandbox = Sandbox.create()result = sandbox.run("python", ["-c", "print('Hello from sandbox!')"])print(result.stdout) # Hello from sandbox!print(result.exit_code) # 0
const result = await sandbox.run("python", { args: ["-c", "print('Hello from sandbox!')"],});console.log(result.stdout); // Hello from sandbox!console.log(result.exitCode); // 0
# Start a Python process inside the sandboxcurl -X POST https://<sandbox-id>.sandbox.tensorlake.ai/api/v1/processes \ -H "Authorization: Bearer $TL_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "command": "python", "args": ["-c", "print(\"Hello from sandbox!\")"] }'
# Timeout is in secondstl sbx exec <sandbox-id> --timeout 10 python -c 'print("hi")'# Run from a specific working directorytl sbx exec <sandbox-id> --workdir /workspace python main.py# Inject environment variables into a single commandtl sbx exec <sandbox-id> --env MODE=prod --env DEBUG=0 /bin/sh -lc 'printf "%s %s\n" "$MODE" "$DEBUG"'# Keep the sandbox after a one-shot run so you can inspect it afterwardstl sbx run --keep /bin/sh -lc 'echo KEEP_TEST && sleep 1'
A verified --env run printed prod 0. A verified --keep run ended with Sandbox <id> kept alive., and tl sbx ls --all then showed that sandbox as running.
# Run with a timeout, working directory, and per-command environmentresult = sandbox.run( "python", ["main.py"], env={"MODE": "prod", "DEBUG": "0"}, working_dir="/workspace", timeout=10,)
Stream stdout/stderr in real time for long-running commands using Server-Sent Events:
CLI
Python
TypeScript
HTTP
tl sbx exec streams combined output to your terminal while the process runs.
# Start a long-running processsandbox = Sandbox.create()proc = sandbox.start_process("python", ["-c", """import timefor i in range(5): print(f"Step {i+1}/5") time.sleep(1)"""])# Stream output as it arrivesfor event in sandbox.follow_output(proc.pid): print(event.line, end="")
const proc = await sandbox.startProcess("python", { args: [ "-c", "import time\nfor i in range(5):\n print(f'Step {i+1}/5')\n time.sleep(1)", ],});for await (const event of sandbox.followOutput(proc.pid)) { process.stdout.write(event.line);}
Use a managed process for long-running services that should restart after a crash or failed health check. Managed processes use the same process API as normal background commands, but opt into supervision when you provide a name, a restart policy, or a health check.
Managed process flags start a background process. In the CLI, these flags require --detach. For blocking one-shot commands that stream output and return an exit code, use plain tl sbx exec or sandbox.run(...).
CLI
Python
TypeScript
HTTP
# Start and supervise a web server. The CLI prints the PID.tl sbx exec <sandbox-id> --detach \ --name dev-server \ --restart always \ --health-http 8080 \ python -m http.server 8080# Inspect the managed processtl sbx ps <sandbox-id> <pid> --json# Manually restart it through the supervisortl sbx restart <sandbox-id> <pid># Stop the process and remove it from supervisiontl sbx kill <sandbox-id> <pid>
Restart policies are never, on_failure, and always. Health checks can be HTTP checks against a local sandbox port and optional path, or TCP checks against a local port. Process user selection accepts a username such as root, a UID string, a uid:gid string, or an object such as {"uid": 1000, "gid": 1000}. The default user is tl-user.
# 2. Connect via WebSocketwscat -c "wss://<sandbox-id>.sandbox.tensorlake.ai/api/v1/pty/<session-id>/ws?token=<token>"
tl sbx ssh requires an interactive terminal and automatically resumes a suspended sandbox before opening the PTY session.For the full programmatic PTY flow, including the READY handshake, binary WebSocket opcodes, and clean shutdown, see PTY Sessions.