---
title: "Sandbox"
description: "6 posts about Sandbox, summarised, each linking to the original."
---

# Sandbox
> 6 posts about Sandbox, summarised, each linking to the original.

## Articles

### [Why Your Sandbox Never Quite Matches Production (And Why That's Fine)](https://yomu.fyi/post/why-your-sandbox-never-quite-matches-production-and-why-that-s-fine.md)
- Company: [Stack Overflow](https://yomu.fyi/company/stack-overflow.md)
- Author: Sancharini Panda
- Published: Oct 13, 2026
- Type: Explainer

The gap between sandbox and production environments is structural and inevitable because they change on different schedules with different triggers. Infrastructure divergence rarely affects what integration tests catch, but behavioral contract drift—when simulated upstream responses no longer match real ones—causes tests to pass while production fails. The most effective teams connect simulation updates to upstream deployment events rather than to test failures, using observation-based tools like Keploy that capture real HTTP traffic to keep simulations current. Full production parity is not the goal; targeted accuracy for the specific behavioral contracts that integration tests validate is sufficient to catch the failures that matter most in distributed systems. The sandbox covers what it can, production reveals what it cannot, and the maintenance work is keeping the sandbox’s coverage accurate within its boundary, not expanding it to match production exactly.


### [Sidecars: A low-latency trust boundary for Sandboxes](https://yomu.fyi/post/sidecars-a-low-latency-trust-boundary-for-sandboxes.md)
- Company: [Modal](https://yomu.fyi/company/modal.md)
- Published: Oct 1, 2026
- Type: Announcement

Modal introduces Sidecars, isolated containers that run alongside a main Sandbox on the same host, establishing a trust boundary between trusted and untrusted code. Sidecars enable communication across trust boundaries at least 3x faster than using separate Sandboxes, reducing latency for operation-heavy agent workloads. The feature addresses the security risk of running an agent’s harness and tool calls together, which creates the “lethal trifecta” of private data, untrusted content, and external communication. Existing solutions either move the harness to a remote service (adding network latency) or rely on egress controls that lack flexibility. Sidecars allow trusted services such as credential injection, proxy traffic, and harness logic to run locally alongside the Sandbox, with independent network policies and dynamic creation via the Modal SDK.


### [Your sandbox can now serve requests](https://yomu.fyi/post/your-sandbox-can-now-serve-requests.md)
- Company: [Boxcompute](https://yomu.fyi/company/boxcompute.md)
- Author: boxy
- Published: Sep 19, 2026
- Type: Announcement

Sandboxes have traditionally been outbound-only machines, unable to receive inbound connections because they sit behind NAT with no public IP or open ports. BoxCompute now enables sandboxes to serve requests by using Tailcat, an open-source library from Tailscale that performs NAT traversal. Tailcat establishes a direct peer-to-peer WireGuard-encrypted path between the client and sandbox, using a DERP relay only for the initial handshake. This approach avoids the latency and bandwidth bottlenecks of relay-based tools like ngrok or Cloudflare Tunnel, and keeps the relay out of the data path. The feature is rolling out as an early preview with scoped, short-lived grants for selected TCP ports.


### [Devin Outposts on Modal](https://yomu.fyi/post/devin-outposts-on-modal.md)
- Company: [Modal](https://yomu.fyi/company/modal.md)
- Published: Jul 21, 2026
- Type: Announcement

Devin, an AI software engineer by Cognition, plans, writes, tests, and ships code semi-autonomously. Cognition now extends Devin with Outposts, moving execution into user-controlled environments while reasoning stays in Cognition’s cloud. Modal is a launch partner with modal-devin, an open-source integration running Outpost sessions in Modal Sandboxes with pre-built custom images, fast cold-starts, snapshotting, and cost-efficient bursting. For example, a task that requires a GPU fails immediately in the default sandbox but succeeds on a Modal-backed Outpost that spins up a GPU on demand and scales to zero when done. One command, uvx modal-devin init, sets up secure infrastructure with a scheduler and worker functions, and each team can have its own outpost with separate credentials.


### [Unpacking sandbox startup latency: why started ≠ ready](https://yomu.fyi/post/unpacking-sandbox-startup-latency-why-started-ready.md)
- Company: [Modal](https://yomu.fyi/company/modal.md)
- Published: Jun 22, 2026
- Type: Problem & solution

Sandbox startup benchmarks measure container boot time, but in production application-level initialization after boot dominates, making container boot the smallest variable. Modal defines a lifecycle with events Created, Scheduled, Started, and Ready, where Ready indicates completion of tasks like git pulls or dependency installs. The gap between Started and Ready can be multiple seconds, directly affecting user-perceived latency for coding agents needing cloned repos and running services. To reduce perceived latency, Modal recommends warm pools that pre-initialize sandboxes using a Queue, combined with Directory Snapshots for per-project customization without rebuilding the environment. Readiness Probes, now generally available, allow defining a shell command that exits 0 or a TCP port that accepts connections, with wait\_until\_ready() blocking until the sandbox is truly ready, simplifying warm pool producer code and providing dashboard events for observability.


### [Building with Modal and the OpenAI Agents SDK](https://yomu.fyi/post/building-with-modal-and-the-openai-agents-sdk.md)
- Company: [Modal](https://yomu.fyi/company/modal.md)
- Published: Apr 15, 2026
- Type: Tutorial

The post walks through constructing a custom agent harness with the OpenAI Agents SDK and Modal Sandboxes, starting from a minimal coding agent that executes shell commands directly on the host. To improve safety, the agent is moved into isolated Modal Sandboxes, which are secure Linux environments that can be equipped with GPUs for compute-intensive tasks like training models. Memory is added via Sessions to accumulate context across turns, and subagents are introduced to handle focused subtasks with fresh context windows, preventing context bloat in the orchestrator while allowing long-horizon work. An async subagent pool enables parallel execution, with quotas to limit GPU spend, and filesystem snapshots allow checkpointing and deduplication of setup work across subagents, saving time and offloading memory. The harness is applied to the Parameter Golf challenge, where an orchestrator delegates parallel training experiments across different ML frameworks on GPUs, demonstrating autonomous research capabilities with composable skills.
