LangSmith/Sandbox
Properties
- created-by
- LangChain
- Managed, isolated environments in LangSmith where agents run arbitrary code and work with a filesystem without touching the infrastructure the agent is deployed on.
- Generally available in the GCP US, EU and APAC regions and in AWS US.
- Used from the
langsmith[sandbox] Python SDK or the langsmith TypeScript SDK (SandboxClient), or from the Sandbox CLI. - LangSmith/Deep Agents can use a sandbox as its backend, which adds the
execute tool alongside the filesystem tools (Sandboxes as agent backends). The same backend interface also accepts third-party providers such as Daytona, E2B, Modal, Runloop and Vercel. Features
- Auth proxy — a proxy sidecar injects credentials from workspace secrets into matching outbound requests, so secrets never live in the sandbox
- also controls egress: HTTP and HTTPS to any host by default, all other raw TCP blocked unless an allow list opens a host and port
- Snapshots — reusable filesystem images, built from a Docker image or captured from a running sandbox, used to boot new sandboxes
- Mounts — attach S3 buckets, GCS buckets and public Git repositories to the sandbox filesystem
- Service URLs — authenticated URLs to HTTP services running inside a sandbox
- Permissions — which workspace members can interact with a sandbox after it is created