Prototype · Preview: every server in the official registry, synced every 30 minutes. Sign in with Google to write reviews.Prototype · updated every 30 min
PopNx MCPMCP servers for people who use AI · explained in plain words

RayTrace

by Godcreatebugsversion 0.17.7i★ 25iRuns on your computerOfficial site ↗
Registry nameio.github.Godcreatebugs/raytrace

How to install

What it does

Local gVisor sandbox for coding agents that records what they actually ran.

  • Connects Runs on your computer
  • Account or key No key needed
  • Category Developer tools

Use together with

Skills that teach the AI this kind of work; they work alongside this one

rea

Reverse engineer anything with agents, from app behavior down to native binaries.

by morluto★ 467,2351 skills

Skill · How-to guide

andrej-karpathy-skills

A single CLAUDE.md file to improve Claude Code behavior, derived from Andrej Karpathy's observations on LLM coding pitfalls.

by multica-ai★ 234,1251 skills

Skill · How-to guideNo license stated

graphify

Turn any codebase, with its docs, SQL schemas, configs, and PDFs, into a queryable knowledge graph. A /graphify skill for Claude Code, Cursor, Codex, and Gemini CLI: local deterministic AST parsing, every edge explained, no vector store.

by Graphify-Labs★ 149,8731 skills

Skill · How-to guide

Why it ranks here

Lists are ordered by a usage score (out of 100) built from these parts

Popularity32/80GitHub stars or weekly downloads: the larger counts 60, the smaller 20
Freshness12/12Full marks for a release or code change within 30 days
Still answering0/8The cloud endpoint answered at the last check
Usage score44/100

Quality: Passed 3/3 basic checks (shown, not used for ordering) · Momentum: 29 (Used only on the Trending tab)

Install

Pick the AI app you use, then copy the settings.

Let your AI install it with one sentence

Please install RayTrace. Follow https://mcp.popnx.com/i/godcreatebugs-raytrace.md, show me the commands and wait for my OK before running them.

Paste it into an AI that can work on your computer (such as Claude Code or Cursor). It reads our steps, shows you the commands and waits for your OK. No key, no sign-up. · See the full text your AI reads

Passed 3/3 checks · Runs on your computer · ✓ Commands checked Nov 19, 2026

First: which AI do you use?

Pick your app and the steps appear below.

Works with Claude, with some setup first

Install Node.js on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone

Let AI install it

Copy this message into a Claude chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server RayTrace for Claude on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "raytrace": { "command": "npx", "args": [ "-y", "@raytrace-cli/cli", "mcp" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the RayTrace tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install Node.js (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    node -v
    • A version number such as v26.13.1 = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed

    Open the Node.js download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v

    Install once; it works for everything that needs Node.js

  2. Open the Claude desktop app’s settings file

    SettingsDeveloperEdit Config

  3. Paste these settings and save the file

    {
      "mcpServers": {
        "raytrace": {
          "command": "npx",
          "args": [
            "-y",
            "@raytrace-cli/cli",
            "mcp"
          ]
        }
      }
    }
  4. Quit Claude and open it again

  5. Try it

    Use RayTrace and tell me what you can do for me, then show me one thing

    ✓ If Claude says it is using RayTrace or shows a RayTrace tool in the answer, you are connected

Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version

ChatGPT cannot connect RayTrace yet

RayTrace runs on your computer, but ChatGPT can only connect servers that run on the web

What you can do instead

A · Use an app that can connect RayTrace

  • Install Node.js on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone
  • Install Node.js on your computer first (one time)
  • Install Node.js on your computer first (one time)
  • Install Node.js on your computer first (one time)

B · Others in Developer tools that work with ChatGPT

Picked from the most used in the same category, only ones that connect by address with no key

Works with Claude Code, with some setup first

Install Node.js on your computer first (one time)

Let AI install it

Copy this message into a Claude Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server RayTrace for Claude Code on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): claude mcp add --scope user raytrace -- npx -y @raytrace-cli/cli mcp 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the RayTrace tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install Node.js (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    node -v
    • A version number such as v26.13.1 = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed

    Open the Node.js download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v

    Install once; it works for everything that needs Node.js

  2. Open Terminal

    Mac: press Command+Space and type Terminal · Windows: open PowerShell

  3. Paste this command and press Enter

    claude mcp add --scope user raytrace -- npx -y @raytrace-cli/cli mcp
  4. Type /mcp in Claude Code

    You should see RayTrace listed as connected

  5. Try it

    Use RayTrace and tell me what you can do for me, then show me one thing

    ✓ If Claude Code says it is using RayTrace or shows a RayTrace tool in the answer, you are connected

Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Works with Cursor, with some setup first

Install Node.js on your computer first (one time)

Let AI install it

Copy this message into a Cursor chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server RayTrace for Cursor on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "raytrace": { "command": "npx", "args": [ "-y", "@raytrace-cli/cli", "mcp" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the RayTrace tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install Node.js (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    node -v
    • A version number such as v26.13.1 = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed

    Open the Node.js download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v

    Install once; it works for everything that needs Node.js

  2. Click this button to open Cursor

    Open in Cursor

    Cursor asks you to confirm; click Install

  3. Open the AI chat in Cursor in Agent mode

  4. Try it

    Use RayTrace and tell me what you can do for me, then show me one thing

    ✓ If Cursor says it is using RayTrace or shows a RayTrace tool in the answer, you are connected

Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Works with VS Code, with some setup first

Install Node.js on your computer first (one time)

Let AI install it

Copy this message into a VS Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server RayTrace for VS Code on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "servers": { "raytrace": { "type": "stdio", "command": "npx", "args": [ "-y", "@raytrace-cli/cli", "mcp" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the RayTrace tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install Node.js (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    node -v
    • A version number such as v26.13.1 = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed

    Open the Node.js download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v

    Install once; it works for everything that needs Node.js

  2. Click this button to open VS Code

    Open in VS Code

    VS Code asks you to confirm; click Install

  3. Open the AI chat in VS Code in Agent mode

  4. Try it

    Use RayTrace and tell me what you can do for me, then show me one thing

    ✓ If VS Code says it is using RayTrace or shows a RayTrace tool in the answer, you are connected

Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Other apps that use MCP, such as Windsurf, Zed or Gemini CLI, each add servers differently. See how in the app list.

See every app that uses MCP →

JSON settings are under “For developers” below

Stuck? Ask people who use RayTrace💬 Discussion →
For developers: Terminal commands and JSON settings

Installed on your computer

Claude Code

claude mcp add --scope user raytrace -- npx -y @raytrace-cli/cli mcp

Claude Desktop (claude_desktop_config.json)

{
  "mcpServers": {
    "raytrace": {
      "command": "npx",
      "args": [
        "-y",
        "@raytrace-cli/cli",
        "mcp"
      ]
    }
  }
}

Cursor (~/.cursor/mcp.json)

{
  "mcpServers": {
    "raytrace": {
      "command": "npx",
      "args": [
        "-y",
        "@raytrace-cli/cli",
        "mcp"
      ]
    }
  }
}

VS Code (mcp.json)

{
  "servers": {
    "raytrace": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@raytrace-cli/cli",
        "mcp"
      ]
    }
  }
}

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

At a glance

Downloads per weeki
1,740/wk
Connection
Runs on your computer
Latest versioni
0.17.7
Published to registryi
Nov 19, 2026
Code last changedi
Nov 19, 2026
Maker
Godcreatebugs
Packages
npm: @raytrace-cli/cli
pypi: raytrace-cli
Registry status
Active

Which apps can use it

Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.

Run on your computer in

ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast

All apps, with pros and cons →

Related guides

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 19, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account Godcreatebugs, which owns the repo

  • ✓ Pass

    Still maintained

    Code last changed today

  • ✓ Pass

    Has a licence

    Uses MIT

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Published vulnerabilities (OSV.dev)

No entries on OSV.dev for @raytrace-cli/cli@0.17.7

Checks only this package version, not every dependency · checked Nov 19, 2026

What we check → · JSON

Makers: ask for a re-check or report wrong info
For makers: add a badge to your README

If you made this, paste this code into your README. The badge links back to this page.

[![Featured on PopNx MCP](https://mcp.popnx.com/badge/godcreatebugs-raytrace.svg)](https://mcp.popnx.com/en/servers/godcreatebugs-raytrace)

Discussion

Ask, share a tip or report that it does not work. Sorted by what people marked helpful.

No posts yet. Be the first to ask or share.

Posts here are written by users, not the PopNx team.

Sign in to post

User reviews

No reviews yet

Sign in to write a review

Compared with others in Developer toolsi

  • More stars than 94% of the other 6116 servers in this category
  • Published to the registry more recently than 99% of the other 6116 servers in this category
  • Basic checks equal to or better than 99% of the other 6116 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is RayTrace safe?

It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed today, and the latest version (0.17.7) reached the registry today.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js, Python (uv) on your computer.

What can I use instead?

In the same category: GitDiagram, Appllama, Cloudflare MCP, Omnara, Repowise

Similar alternatives

Same category, other makers, commands already checked. Official ones first, then by stars.

Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

GitDiagram

Architecture diagrams, explanations and Mermaid source for public GitHub repositories.

by ahmedkhaleel2004Widely used★ 19KUpdated 2 months ago

Runs in the cloud✓ service owner · gitdiagram.comTried by the PopNx team

Appllama

Study screens, flows and paywalls from top-earning iOS apps, then build from what wins.

by AppllamaWidely used★ 5.2KUpdated 3 months ago

Runs in the cloud✓ service owner · appllama.io

Repowise

Codebase intelligence for AI coding agents: graph, git history, docs, decisions, code health.

by repowise-devWidely used↓ 6.5K/wk★ 8.2K Stars for the whole repoUpdated 6 days ago

Computer or cloud✓ service owner · repowise.dev
Compared with similar ones
This one
RayTrace
GitDiagramAppllamaCloudflare MCPOmnaraRepowise
Runs whereInstalls on your computerRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to installCloud or install on your computer
Needs a keyNoNoNoNoNoNo
Add with + in ClaudeNoNoNoYesNoNo
Basic checks3/34/44/44/44/45/5
LicenseMITMITMITApache-2.0Apache-2.0AGPL-3.0
PriceNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registry

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

Eye of Sauron

See what your coding agents did, rather than what they said they did.

Try the interactive demo — no install needed

Website · npm · PyPI · MCP · Contributing · Report an issue

Why sandboxing matters

A coding agent doesn't just suggest edits. It runs commands, installs packages, reads and writes files, and opens network connections — often with permission to do all of that on your machine.

What it tells you afterwards is a claim. "Tests passed" is what the agent reported. That report can miss a command that phoned home, a package you didn't ask for, a file outside the task, or a test whose real exit code was not zero. And if the agent is running on your laptop, it can reach everything else there: secrets, private networks, and files that were never part of the work.

Sandboxing is how you change both of those problems. The agent works in an isolated copy of the project, where it cannot see your machine. And the record of what happened is taken from outside that sandbox, so the agent cannot turn it off or edit it.

Why we built RayTrace (1 min 47 sec)

*Why we built RayTrace — the gap between what an agent reports and what actually ran.*

How RayTrace sandboxes

RayTrace runs Claude Code or Codex in that isolated copy, records what actually happened, and shows it in a dashboard.

Each local sandbox is a Docker container under gVisor, inside a Linux VM made with Lima. It can't see your machine's files or private networks. A collector outside the sandbox — which the agent can't turn off — records every command, its real exit code, the files it read or changed, and where it connected. Your own files are never changed. Nothing is uploaded.

The dashboard has two layers. Tool calls are what the agent reported. Sandbox evidence is what the machine saw. If those disagree, you can see it, and take the file diffs home as a patch.

Local sandboxes are free, MIT licensed, and need no RayTrace account. Cloud sandboxes are optional, for teams that want a shared dashboard at app.raytracer.si.


Create a local sandbox

Install the CLI from npm or PyPI, then create a sandbox in any Git repository. Nothing is uploaded.

npm install -g @raytrace-cli/cli

or: pip install raytrace-cli

or: uv tool install raytrace-cli

cd your-project # any Git repository raytrace sandbox create --local # first time: sets up the VM, a few minutes raytrace connect your-project --claude # a terminal in it, with Claude Code running

open the local dashboard at http://127.0.0.1:8797

  • The sandbox is named after the folder. Use --name my-box to choose the name.
  • Use --codex instead of --claude to start Codex, or leave both off for a plain shell where you run claude or codex yourself.
  • connect prints a link to the dashboard showing only this sandbox's prompts. The full local dashboard is at http://127.0.0.1:8797 — open that in your browser. If you set RAYTACE_PORT in ~/.raytrace/config.env, the dashboard is on that port instead.

The npm package needs Node.js 22.13 or newer (node --version) on macOS or Linux. The PyPI package installs the same CLI with its own Node.js, so you don't need Node on the machine. Windows is experimental. Where this page says npx -y @raytrace-cli/cli@latest, use uvx --from raytrace-cli raytrace instead.

Or skip the commands and ask your editor's agent: set up MCP, then say "create a local sandbox and connect this repo".

What you need
Requirement
macOS 13.5 or laterNothing to install. RayTrace uses your Lima 2.0+ if you have it, or offers to download Lima into ~/.raytrace/lima (no admin rights; checked against a pinned checksum)
Older macOSQEMU too: brew install qemu
LinuxLima, QEMU, and access to /dev/kvm (sudo usermod -aG kvm $USER, then log out and in)
Windowsexperimental; RayTrace doesn't download Lima there, so local sandboxes need WSL2 — see docs/windows.md for what works and the WSL2 and cloud paths
Disk and memorythe first setup downloads about 1 GB; the VM uses 4 GiB of memory while it runs

raytrace doctor checks all of this and says how to fix anything missing.

Day to day
raytrace sandbox list --local         # your local sandboxes

raytrace connect my-box --claude # back in; the sandbox keeps running when you leave raytrace sandbox stop my-box # stop it; its files are kept raytrace sandbox start my-box raytrace sandbox destroy my-box # asks whether to delete its captured logs too limactl stop raytrace # stop the whole VM to free its 4 GiB of memory

When you destroy a sandbox, you're asked what to do with its logs:

  • Yes deletes them everywhere, the dashboard and Playground forks included.
  • No moves them to ~/.raytrace/archive/ - /: the agent transcripts, the recorded commands, files and connections as JSON lines, and any forks. Its sessions stay in your dashboard.

--delete-logs or --keep-logs answers without asking. To keep the logs in the cloud, raytrace upload logs --sandbox my-box sends them to app.raytracer.si (needs a sign-in).

How it works
  • Isolation: each sandbox is a Docker container under gVisor, inside a Linux VM made with Lima. It can't see your machine's files or private networks. A copy of your project goes in (picked the same way as for cloud uploads); your own files are never changed.
  • Resources: each sandbox gets 2 GB of memory, 2 CPUs, 256 processes and a 512 MB /tmp. All sandboxes share the VM's 30 GiB disk.
  • Recording: a collector outside the sandbox, which the agent can't turn off, records every command, file change and network connection. Claude Code's prompts, answers and tool calls go to your local dashboard as well. Nothing leaves your machine.
  • Changes: the project is snapshotted after every edit, so Changes in the dashboard shows what each prompt left different, with a patch to take home.
  • Playground: rerun a session from any step with something changed (a tool result, a file, the model or the message) and compare the outcomes, optionally with a check such as npm test. Each rerun is a fork, a sandbox of its own started from the snapshot just before that step.
Inside the sandbox

Claude Code and Codex are preinstalled. --claude starts Claude Code with --dangerously-skip-permissions, and --codex starts Codex with --dangerously-bypass-approvals-and-sandbox. The sandbox's own settings, which the agent can't change, make this the default too, so typing claude or codex yourself works the same way. The sandbox is what keeps the agent contained, and every command is recorded.

Files a project's owner restricts in the dashboard (Initial scan) can't be changed by the agent, whatever it tries. Sign in to Claude Code or Codex inside the sandbox, as you would on your machine; the sign-in stays until you destroy it. Exiting the agent drops you into the sandbox's shell, and exiting that leaves the sandbox running. raytrace connect takes you back.

In local sandboxes, Codex's prompts don't reach the dashboard's Prompts page yet. Its commands, file changes and network connections are recorded.


What a recorded session shows

Cloud sessions are at app.raytracer.si. The local dashboard is at http://127.0.0.1:8797 — open that in your browser. Every page is about one prompt, and they link to each other.

The dashboard has two layers. Tool calls are what the agent reported: the path from your prompt to the answer, with the command, what the agent says came back, and tokens, time and cost at each step. Sandbox evidence is what the machine saw, recorded from outside the agent where it can't be turned off or edited: every process, its real exit code, the files it read or changed, and where it connected.

FeatureWhat it does
PromptsEvery prompt you gave the agent, newest first, with where it ran (your machine, a local sandbox or a cloud sandbox), the model, how many tool calls it took and what it cost. Open one to read the answer and a short recap of the run.
Tool callsThe path from your prompt to the answer: one divider for each round trip to the model, one row for each tool call it proposed, with the command and what the agent says came back, plus tokens, time and cost at each step.
Sandbox evidenceWhat the sandbox itself saw, recorded from outside the agent. Every process in time order, with its real exit code, the files it read or changed, and where it connected — including anything no tool call accounts for. Use it to check "tests pass" against the real exit code, and to catch a script that phoned home or a package you didn't ask for.
ChangesEvery file the prompt changed, with its diff, first for the whole prompt and then step by step. Download it all as one patch and apply it to your own checkout. The sandbox works on a copy; the patch is how you take the work home.
ContextWhat was in the model's context when it answered: what you said earlier, what the model brought in itself (earlier answers, and the files it read, with how much of each actually fit), and what the agent's harness adds to every request. Use it to see whether a wrong answer came from a file that was never read, or was cut off.
PlaygroundPick any step and rerun from there with something changed: a tool result, a file, the model, the message, or a time limit. Each rerun is a fork, a sandbox of its own started from the snapshot just before that step. Add a check such as npm test and every fork is graded pass or fail, so you can compare models or outcomes side by side.

| Story | The short version of a long run: a timeline of only the steps that mattered, the single most consequential command pulled out at the top, and for each step what the agent could see, what it proposed, what really happened and what that led to. Worked

Only the beginning is shown; read the rest in the repo