RayTrace

RAYTRACE CLI / LOCAL SANDBOX · V0.5.0

Your machine.
Your sandbox.
One CLI.

Run your coding agent in an isolated local sandbox with raytrace-cli. Keep your project and recorded sessions on your machine, and inspect what the agent did in your local dashboard.

Watch the setup walkthrough View on GitHub ↗

Available in CLI 0.5.0+. macOS and Linux supported; Windows experimental. No RayTrace account required.

FROM INSTALL TO YOUR FIRST LOCAL RUN

Set up your sandbox.
See every step.

Install the npm package, create a sandbox from a Git project, and launch Claude Code. Then open your local dashboard to inspect the run.

Install with npm install -g @raytrace-cli/cli@latest and check raytrace --version is 0.5.0 or newer. Run raytrace doctor to inspect prerequisites. From your Git project, run raytrace sandbox create --local --name demo-box, approving the Lima download if asked. First-time VM setup takes several minutes. Run raytrace connect demo-box, then claude inside the sandbox and sign in to Claude Code if prompted. In another terminal on your machine, run raytrace open to inspect local sessions and sandbox evidence.

CLI 0.5.0 workflow. Example output and agent/dashboard screens are illustrative. First-time setup is compressed.Watch full screen →

1. Install and check the CLI

Start with Node.js 22.13+, npm, and Git on your machine. Check that RayTrace is version 0.5.0 or newer.

npm install -g @raytrace-cli/cli@latest
raytrace --version
raytrace doctor

2. Create a sandbox from your project

Replace your-project with your Git repository’s path. The --local flag keeps the sandbox on this machine; omitting it creates a cloud sandbox.

cd your-project
raytrace sandbox create --local --name demo-box

If Lima is missing, the CLI asks to download it. The first run sets up the Linux VM, gVisor, and agents; allow several minutes, about 1 GB of downloads, and 4 GiB of memory while the VM runs. Your source project is copied into the sandbox.

3. Connect and launch Claude Code

raytrace connect demo-box
claude

Run claude inside the sandbox terminal and sign in with your Claude account if prompted. Provider calls use that account; RayTrace keeps the captured record locally.

4. Review the run

In a second terminal on your machine, or after exiting the sandbox shell:

raytrace open

Open Sandboxes to find demo-box and its prompts. Follow tool calls into Sandbox evidence to inspect recorded commands, file changes, and network connections.

Pause and resume

Stopping a sandbox keeps its files. Start it again when you want to continue.

raytrace sandbox stop demo-box
raytrace sandbox start demo-box
raytrace connect demo-box

BUILT INTO THE CLI

Local by choice.
A familiar workflow.

The same CLI manages your sandbox from creation to connection, with setup checks for your platform.

01 / RUN LOCALLY

Start on your machine.

A local environment for your project and agent, managed through raytrace-cli.

02 / PLATFORM CHECKS

A familiar workflow.

One CLI entry point, with platform-specific setup and requirements documented in the repository.

03 / OPEN SOURCE

Built alongside the CLI.

Explore the source, read release notes, and share your workflow on GitHub.

Share feedback ↗

ALSO AVAILABLE / CLOUD PREVIEW

Prefer a hosted sandbox?

Create a cloud sandbox and review its sessions with your organization in the hosted RayTrace dashboard.

Get started in the cloud →