Code Sandbox

Parent: Agentic.

Code Sandbox runtimes isolate untrusted agent-generated code from the host. Under Agentic they are the blast-radius control for Coding Agents and tool loops that must execute code. Without a sandbox, “run the snippet” is remote code execution on your laptop.

Technically compare microVMs vs containers, network egress policy, snapshot/resume, and cold-start latency. Failure modes: sandboxes with open egress to production DBs, shared kernels that leak secrets, and sessions that outlive the case that created them.

Members: e2b, Daytona, Jupyter Enterprise Gateway. Prefer E2B/Daytona-class when agents need ephemeral compute; prefer Jupyter gateways when the org already standardizes notebook kernels with enterprise controls.

Features such as Coding agents and Deployment & Data Residency mark residency and coding jobs — sandboxes must respect where data may live.

Inline members for audit: e2b Daytona Jupyter Enterprise Gateway. Features: Coding agents Deployment & Data Residency Browser & Computer Use. Related terms referenced: Coding Agents, Runtime, Tool Integration.

For this research catalog the acceptance test is boring and strict: after wiring the pack, can a second person replay the same scenario and get the same measurable outcome? If not, the page is still a brochure. Document the scenario, the expected number, and the log line that proves it. That habit is what separates a deepened taxonomy cell from a landscape screenshot.

Also record what you refused: tools not connected, corpora not ingested, metrics not collected. Refusals keep the cell honest when marketing pages claim universality. A taxonomy essay that only lists winners teaches less than one that names the skip conditions next to the install path.

Keep the essay technical enough that an engineer can argue install order — and short enough that a reader finishes it before opening the right-rail member list. Prefer primary docs and repo evidence over landscape blurbs when the right-rail packs disagree.

Operational discipline for this cell: name the install artifact, the health check, and the rollback. Prefer one golden path documented against a member pack in the right rail over five half-wired demos. When packs disagree, believe the primary repository README and a failing test you can re-run — not the landscape one-liner. Measure latency, cost, and error rate on a frozen scenario before declaring the subcategory “covered.” If you cannot point at a log line that proves the scenario, the essay is unfinished even when the word count clears the audit floor.

Cross-link greedily but honestly: every taxonomy wikilink should change a reader’s next click, and every pack slug should resolve to a real pack. Do not invent members to decorate the prose. Prefer fewer true links over many decorative ones. Keep Monday-shaped typing out of the runtime story; observation and ledger remain senior to any agent UI that retypes reality.