GET STARTED WITH RAYTRACE
Record your first
agent session.
Install RayTrace, sign up from the CLI, create a cloud sandbox from your project, and run your agent there. Then inspect the prompts, tool calls, and executed commands in the hosted dashboard.
You’ll need Node.js 22.13+, npm, and a Git project. RayTrace does not ask you for an API key.
Install the latest RayTrace CLI, check your version is 0.4.0 or newer, authenticate in your browser, create a cloud sandbox from your project, connect, and launch the preinstalled Claude Code.
From CLI install to Claude Code in a cloud sandbox. Browser and agent screens are illustrative.Watch full screen →
Commands
Install and sign in
npm install -g @raytrace-cli/cli@latest
raytrace --version
raytrace auth loginCheck that your CLI version is 0.4.0 or newer. Login prints a short code and opens a browser approval page; approve it, then check which account you are using with raytrace auth status. You can also create a sandbox from your browser: open app.raytracer.si, sign in, and drop a project folder on the Sandboxes page — you see what would be uploaded before anything is sent.
Everyday commands
| Command | What it does |
|---|---|
raytrace auth login|status|logout | Sign in to RayTrace, inspect your sign-in, or remove it from this machine. |
raytrace sandbox create [--name <name>] | Upload the current Git project to a new cloud sandbox. A later create makes another sandbox; it does not sync changes into an existing one. |
raytrace sandbox list | List your cloud sandboxes. |
raytrace connect [id] | Open an interactive terminal in a sandbox (also raytrace sandbox shell [id]). Omit the ID only when you have one live sandbox. |
raytrace sandbox start|stop [id] | Resume or stop a sandbox; stopping keeps its files. |
raytrace sandbox destroy [id] | Delete the sandbox and any agent sign-in inside it. On Beta its traces go too; on paid plans you are asked whether to keep them until your retention date (--keep-traces in scripts). Destruction asks you to type the ID to confirm — export any work you want to keep first. |
raytrace help | Show commands. |
Remove RayTrace
Destroy any sandboxes you no longer need, sign out, then remove the package:
raytrace sandbox destroy <sandbox-id>
raytrace auth logout
npm uninstall -g @raytrace-cli/cliSigning out removes your sign-in from this machine; it does not stop or destroy cloud sandboxes. Recorded sessions are kept for your organization.
Privacy & release scope
Cloud sandboxes run on RayTrace’s servers. Creating one uploads your project; prompts, requests, answers, tool calls, and executed commands are recorded there for your organization. Organization members can review the sessions in the hosted dashboard. Destroying a sandbox deletes its files and agent sign-ins. On Free its recorded evidence goes too; on Pro and Enterprise you choose whether to keep it until your retention date.
What leaves your machine
A local sandbox stays on your machine, and nothing about it is sent unless you run raytrace upload logs. That command shows the sandbox, its dates and size, asks you to confirm, and sends only that sandbox’s evidences: prompts, model responses, tool calls and kernel-level activity, gzipped. Other sandboxes, your project files and your sign-ins are not included. Credential-shaped fields are withheld when recorded, but prompts and tool output can still contain secrets, so check before you upload. Members of your organization can see what you upload, according to their role. Uploaded evidence is what your machine reported, not evidence RayTrace collected independently, and the dashboard marks it Local.
Your CLI sign-in is kept in the macOS Keychain or Linux secret service, with a file readable only by you as a fallback. raytrace auth logout removes the sign-in from your machine; it does not stop or destroy cloud sandboxes.
Evidence boundaries
A transcript’s reported tool result is separate from independently observed execution evidence. A command starting or exiting successfully is not proof of a correct outcome. RayTrace does not reconstruct a model’s private chain of thought.
What gets uploaded
Creating a sandbox uploads the files Git would track, including new files not ignored by Git. It excludes .git, dependency directories such as node_modules, common build output, .env*, private keys (.pem, .key, .p12, .pfx), and common credential files such as .npmrc and .netrc. Symlinks are skipped. A folder dropped in the dashboard follows the same rules. Review your files before uploading: exclusions cannot detect secrets embedded in ordinary source files.
Limits: a project may be up to 200 MiB and 20,000 files before compression, with no single file over 25 MiB, and 100 MiB once packed; a project over a limit is refused with the files named, and nothing is uploaded. How many live sandboxes you may run depends on your plan (3 on Free, 5 on Pro) — see Pricing. Cloud sandboxes are a preview; report a preview issue.