Genko 原稿Back to edition

Sandman: Building and Operating Sandboxes for Agentic Reinforcement Learning on Shared Kubernetes

Amazon runs agent reinforcement learning on shared Kubernetes with sandbox pods. Four SWE-bench Verified campaigns created 3.1 million sandboxes in October 2026.

The explainer · 256 words

The claim

Amazon runs agent training in sandboxes that scale to millions of environments.

The problem

Agent training needs thousands of short-lived tool environments in bursts.

Those bursts share clusters with other production jobs.

Slow setup and abandoned sandboxes can stall training.

How it works

Each sandbox is a Kubernetes pod with a small mounted daemon.

The daemon runs inside the unmodified task image.

A framework sends a task image and runs commands in the sandbox.

Files and processes persist until the framework releases the environment.

Sandman manages creation, readiness, cleanup, and reclaims abandoned sandboxes.

Figures

Scale test versus October productionSandman in two settings.
Scale test · 11,858 sandboxesOctober 2026 · 3.1 million sandboxes
Concurrent tiny sandboxes held at once.
Created by four SWE-bench Verified campaigns.

50% October 2026 · 50% Scale test

Sandbox life cycleSandman owns every stage.

Step 1 of 5

Task image

The framework supplies an unmodified task image.

What one sandbox doesLife-cycle facts from the paper.

Sandbox property

Unit

One Kubernetes pod with a mounted daemon.

What changes

A scale test held 11,858 concurrent tiny sandboxes.

Four SWE-bench Verified campaigns created 3.1 million sandboxes in October 2026.

Limits

The paper reports design trade-offs and lessons, not baseline comparisons.

The daemon, provider, and pool will be open-sourced later.

The paper gives no cost or latency figures for sandboxes.

Source · arXiv

arxiv.org/abs/2610.39711cs.DC · cs.AI · cs.LG

More from this edition