Give agents
a secure runtime
Ephemeral, isolated sandboxes designed for agent-generated code.
Run untrusted code safely
Spin up ephemeral microVMs for agent-generated code. Agents get full root inside the sandbox, so they can install packages, run Docker, and do anything else you'd do on a Linux box. Your core infrastructure and other workloads stay untouched.
.avif)
Sub-second starts
Spin up hundreds of sandboxes in parallel with one SDK call. Prewarming keeps p50 latency under 1.12s, so agents get an environment the moment they need one.

Built for long-running, statefulwork
Sessions run over WebSockets with streamed output, and state persists across threads. Sandboxes stay alive only as long as you need.
.avif)
Resources for LangSmith Sandboxes
FAQs for LangSmith Sandboxes
Sandboxes are isolated environments that run agent code without affecting your main infrastructure. Each one uses microVM isolation and is ephemeral by default. Learn more.
Bring your own Docker image or start from a template. Templates let you define container images, resource limits, volumes, and Auth Proxy configuration, then reuse them across sandboxes. Learn more.
The Auth Proxy injects credentials into outbound API requests from the sandbox, so your agent can call external services without secrets ever touching the runtime. Learn more.
No. Sandboxes are framework agnostic. They work with the Python and TypeScript LangSmith SDKs and integrate with Deep Agents, but you can use them with any framework or none at all. Learn about LangSmith Sandbox SDK.
Anything you can package in a Docker image runs inside a sandbox. The Python and TypeScript SDKs are available for creating and managing sandboxes from your code. Learn about LangSmith Sandbox SDK.
See our pricing page for more information, and find a plan that works for you.
Ready to ship agents that execute code?
Give your agents an isolated runtime without exposing your infrastructure. Spin one up in a single SDK call.

