langchain-superserve
Superserve sandbox integration for Deep Agents. Because Deep Agents compiles to a LangGraph graph, this works across LangChain, LangGraph, and DeepAgents.
Quick Install
pip install langchain-superserve
Deep Agents SDK
from superserve import Sandbox
from langchain_superserve import SuperserveSandbox
# Launch from a python-equipped template so the agent's file tools work (see below).
sandbox = Sandbox.create(name="my-agent", from_template="superserve/python-3.11")
backend = SuperserveSandbox(sandbox=sandbox)
try:
result = backend.execute("echo hello")
print(result.output)
finally:
sandbox.kill()
Pass the connected SuperserveSandbox as the backend to
create_deep_agent(...) to run the agent's shell and file operations inside a
Superserve microVM.
Deep Agents Code
Installing this package registers a superserve sandbox provider for the
deepagents-code (dcode) terminal agent:
dcode --install langchain-superserve --package
export SUPERSERVE_API_KEY=ss_live_...
dcode --sandbox superserve
The provider defaults to the superserve/python-3.11 template; override with
SUPERSERVE_TEMPLATE.
Requirements
SuperserveSandbox adapts a Superserve sandbox to the Deep Agents sandbox
protocol. The protocol synthesizes ls/read/edit/glob (and the write
preflight) with in-sandbox python3, so launch from a python-equipped
image — superserve/python-3.11, superserve/python-ml, or
superserve/code-interpreter. execute, grep, and file upload/download work
on any image, including the minimal superserve/base.
Superserve extras
Beyond the standard backend, Superserve sandboxes offer pause()/resume() for
idle cost savings and proxy-brokered secret binding
(Sandbox.create(secrets=...)) so real credentials never enter the sandbox.
Manage these through the Superserve SDK on the sandbox you pass in.
Development
uv sync --group test
make test # unit tests (no network)
make lint # ruff + ty
SUPERSERVE_API_KEY=ss_live_... make integration_tests # standard suite, live
Integration tests create a real sandbox from superserve/python-3.11 (override
with SUPERSERVE_TEMPLATE) and skip cleanly when SUPERSERVE_API_KEY is unset.
Release files for langchain-superserve 0.0.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| langchain_superserve-0.0.1.tar.gz | 233.1 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| langchain_superserve-0.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 240.9 kB
Release files / langchain_superserve-0.0.1.tar.gz
| Download URL | langchain_superserve-0.0.1.tar.gz |
|---|---|
| Size | 233.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
506cae41bf8569c1cfff2e50b4c666445aa5cfea940dd85538991f366d18cc7a
|
|
BLAKE2b-256 checksum How to use checksums |
341b86f0a0b8d979b15999297d910183f8d709bf8b3785bf4f547a188fb32899
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.13
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 26, 2026.
Transparency logRelease files / langchain_superserve-0.0.1-py3-none-any.whl
| Download URL | langchain_superserve-0.0.1-py3-none-any.whl |
|---|---|
| Size | 7.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d2c1aa73cc6f71a309956810a6d9bb64a415223ae704e08997dcd7da2c8efd32
|
|
BLAKE2b-256 checksum How to use checksums |
f090025a04d87a9527cd3346a6d4ded2b72084b32fbf03aabf4736354b5b463b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.13
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 26, 2026.
Transparency log