The agent swarm platform. Thousands of agents in parallel, each in its own Ubuntu microVM with root, Docker and nested KVM. Pay per second. ✨https://nitter.cf/t.co/h3pD789f2G
inside of a superfast VM
Joined October 2026
- Tweets45
- Following2
- Followers9
- Likes1
Git worktrees or one machine per agent? Worktrees are enough while agents only edit and test code. Once they run dev servers, databases or Docker, give each its own machine so they can all bind the same port without clashing.
northbayventures.com/running…
Using Sandboxer from Python? Install sandboxer-sdk, then import sandboxer.
pip install sandboxer-sdk
Don't pip install sandboxer: that PyPI package is an unrelated project.
northbayventures.com/sandbox…
Kubernetes inside a sandbox: it's a full VM with Docker preinstalled, so kind create cluster gave us a Ready node in about 28 seconds in one run on a default sandbox, and the k3s install script about 13 seconds. Then sbx host the port for an HTTPS URL.
sandboxer.com/guides/run-kub…
One agent, three steps: build in a Sandboxer sandbox, ship behind a Flagger.gg flag (live by default unless marked not ready), then launch with creator posts on Transformer.
Separate products, one studio, and a person sets the limits.
northbayventures.com/sandbox…
Fresh sandbox per tool call, or one per session?
Reuse one sandbox when calls build on each other. Use a fresh one per call for untrusted input, started from a pre-warmed named snapshot so it's ready without reinstalling deps.
northbayventures.com/sandbox…
CLI tip: run sbx ssh-config --install once. It adds a Host *.sbx entry to ~/.ssh/config, so ssh, rsync and VS Code or Cursor Remote-SSH reach any sandbox as <id>.sbx, tunneled over HTTPS with no open ports.
sandboxer.com/guides/ssh-int…
Can an agent use your product without the website? A 7-point checklist from the studio behind Sandboxer: an API for every action, JSON from the CLI, an MCP server, narrow revocable keys, safe retries, an audit trail and an llms.txt.
northbayventures.com/make-yo…
Need to close your laptop mid-session? The local Sandboxer MCP server (sbx mcp) has a handoff_session tool. It moves a local Claude Code or Codex session and its repo into a new sandbox and resumes the agent there.
northbayventures.com/sandbox…
Does sbx fork copy memory? No.
A fork copies a running sandbox's disk into a new, independent sandbox. The copy boots fresh, so no RAM and no running processes come across. Files written up to the fork are there.
sandboxer.com/guides/fork-a-…
When an agent at North Bay Ventures says "fixed", it means deployed and checked in production. Each report has the same shape: what changed, the pull request, the deployed commit, proof it's live, and anything that needs Jon. Proof beats confidence.
northbayventures.com/how-the…
What a sandbox fork doesn't inherit:
- auto-stop: the default one hour applies unless you pass a TTL
- hosted URLs: tokens aren't copied, so run sbx host again
- identity: it gets a new id, subdomain, machine-id and SSH host keys
northbayventures.com/sandbox…
10 sandbox creates at once, measured Oct 28 from Virginia through sandboxer.com: all ready within 0.39 s in us-east and 0.59 s in eu-central, default size. The eu-central figure includes the round trip to Finland.
sandboxer.com/docs/machines?…
Sandboxer is built with AI agents that write and review code, run tests and prepare deploys.
The rules that keep it safe: every change has tests, risky changes get an independent review, and every deploy is checked in production and can be rolled back.
northbayventures.com/how-we-…
A sandbox can pause itself after a set number of idle minutes, memory included, and wake on the next API call or request to one of its hosted URLs.
sbx new --idle 60 pauses after an hour without activity.
sbx idle <id> 0 means never pause this one.
northbayventures.com/sandbox…
After every resume, read memoryRestored.
true: memory came back and processes kept running.
false: it booted from disk with your files, and resumeReason says why: cpu_mismatch, resized, no_memory_snapshot or restore_failed.
sandboxer.com/guides/detect-…
Why does Sandboxer exist? Agents have made software much cheaper to build, and they've created a new need: a safe place to run the code they write.
That's the studio's answer in its FAQ, along with who runs it and where:
northbayventures.com/faq/
Three ways to redirect a coding agent mid-task:
sbx prompt queues the next task; the running turn finishes first.
sbx steer adds an instruction; the agent takes it into account and continues.
sbx interrupt stops the turn and discards it.
northbayventures.com/sandbox…
Give your agent its own cloud computer, with nothing to install. Add sandboxer.com/mcp as a connector in Claude, ChatGPT, Cursor or Codex and sign in. It can then create Linux sandboxes, run code, move files and put a port on a public HTTPS URL.
sandboxer.com/docs/mcp?utm_s…
No staging server. Each change deploys switched off, then turns on deliberately: admins first, then named users, then a sticky percentage, then everyone. An unknown or failed flag check counts as off. How North Bay Ventures ships, Sandboxer included:
northbayventures.com/feature…
The agent inside each Sandboxer VM talks to the host over vsock, not TCP. So nothing on the sandbox's network, not even code running as root, can reach the host's control API.
That's one of four isolation layers. The rest, plus the network policy:
northbayventures.com/sandbox…