Run a code review in an isolated sandbox

Hand a branch to an agent and let it run your tests on the core — in an isolated sandbox, against the data you connected.

You have a PR. CI hasn't finished, or CI doesn't run the test you care about, or you want a second opinion on what's failing and why. Drop the branch into a connect0 sandbox and have an agent investigate.

The plan

1. Export the branch as a tarball.
2. Upload it via upload.create_link.
3. Have the agent unpack, install deps, run tests, report failures inline.

1. Export the branch

git archive --format=tar.gz HEAD -o branch.tar.gz
wc -c < branch.tar.gz   # → 4194304

git archive skips .git/, node_modules/, anything in .gitignore — exactly what you want.

2. Upload

> I'm sending you a snapshot of my feature branch. Make me an upload link for branch.tar.gz, 4,194,304 bytes, application/x-gzip.

You PUT. Agent confirms via info's recent_uploads.

3. Unpack and test

> Unpack it under /workspace/branch, run npm install, then npm test, and tell me what failed and why.

Agent:

sh "mkdir -p /workspace/branch && tar -xzf /workspace/archives/branch.tar.gz -C /workspace/branch && cd /workspace/branch && npm install"
sh "cd /workspace/branch && npm test 2>&1 | tail -100"

The agent reads the output, finds the failures, asks you about each one or proposes fixes.

Why this beats local CI

• Reproducibility. The sandbox is clean — no leftover state from your last branch, no half-installed deps from a git stash you forgot.
• Resource isolation. Long-running tests don't eat your local CPU.
• Asynchronous. Drop a branch, walk away, come back to the agent's report.
• The agent has context across runs. Drop multiple branches into the same project's workspace; info shows the agent which one is "current."

Egress matters

If your tests need to hit external APIs (npm install from npmjs.org, integration tests against a third-party service), flip egress to open on the project. The default restricted is right for local-only tests; explicit-open is right for anything that does network calls.

Cleanup

Once a branch is reviewed, remove the archive + the unpacked tree:

sh "rm -rf /workspace/branch /workspace/archives/branch.tar.gz"

Storage is cheap but persistent — five reviews of five branches add up to real bytes.

Limits

• Token cost on big test outputs. A failing test suite spitting 10,000 lines of stack traces gets truncated at 64 KiB by sh. Run failing tests one at a time via -t <test-name> so the per-call output is bounded.
• No download.create_link yet. If the agent generates a coverage report you want to keep, see the download workaround until the native download surface ships.

Next steps

• Iterate on a config file with the agent.
• Audit: who uploaded what, and when.

Where this fits

This is the Run your agents pillar of connect0 — the core that connects everything your company runs on. The agent runs your suite in a clean, isolated per-project sandbox on the core — no leftover state, no local CPU, a report waiting when you come back. Start building → · All guides →