The repository or configuration that created this release differ from a previous release. View details.
langchain-leap0
Leap0 integration for LangChain Deep Agents: a BaseSandbox backend that runs shell commands and file transfers inside a Leap0 sandbox.
Leap0 is enterprise-grade cloud sandboxes for AI agents. Launch isolated sandboxes in ~200ms. Give every agent its own compute, filesystem, and network boundary while your agents run safely.
Quick install
pip install langchain-leap0
Set your API key (see Leap0 for account and key management):
export LEAP0_API_KEY="your-key"
Minimal usage with the [leap0](https://pypi.org/project/leap0/) SDK and Leap0Sandbox:
from leap0 import Leap0Client
from langchain_leap0 import Leap0Sandbox
client = Leap0Client()
sandbox = client.sandboxes.create()
backend = Leap0Sandbox(client=client, sandbox=sandbox)
try:
result = backend.execute("echo 'Hello LangChain from Leap0.dev'")
print(result.output)
finally:
client.sandboxes.delete(sandbox)
client.close()
Examples
Runnable scripts for Deep Agents sandboxes. See [examples/README.md](examples/README.md) for environment variables and how they map to LangChain **SandboxIntegrationTests**.
| Script | Summary |
|---|---|
| examples/basic_sandbox.py | Minimal: create a sandbox, Leap0Sandbox.execute(), teardown. |
| examples/deep_agent_sandbox.py | create_deep_agent(..., backend=Leap0Sandbox(...)) — create and run a script; prints a short execute summary. |
From the repo root:
uv run python examples/basic_sandbox.py
uv run python examples/deep_agent_sandbox.py
Developing from source
From this directory (alongside leap0-python in the Leap0 workspace). Uses pyproject.toml dependencies; run:
cd langchain-leap0
uv sync --all-groups
Running tests
From the package root:
# Unit tests
make test
# LangChain standard sandbox integration tests
make integration_test
Integration tests require:
export LEAP0_API_KEY="your-key"
Documentation
Full documentation is available at leap0.dev/docs.
License
Apache License 2.0. See LICENSE for details.
Metadata
Release files for langchain-leap0 0.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Change of provenance
The repository or configuration that created these release files differ from that of a previous release.
We recommend inspecting the repository and configuration before proceeding. View details.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| langchain_leap0-0.2.0.tar.gz | 8.9 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| langchain_leap0-0.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 17.4 kB
Release files / langchain_leap0-0.2.0.tar.gz
Change of provenance
This file belongs to a release with changed provenance: the repository or configuration that created the release files differ from that of a previous release.
We recommend inspecting the repository and configuration before proceeding. View details.
| Download URL | langchain_leap0-0.2.0.tar.gz |
|---|---|
| Size | 8.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
76cee0a1ae3dbdfcf4ce02599f5e5ee964ae11e49c44d05848986e6d97c145d2
|
|
BLAKE2b-256 checksum How to use checksums |
761669b97aebed6d0f9c0fb36ece5fc6d9534f41808e4f86ee77a5a652c28a39
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Apr 12, 2026.
Transparency logRelease files / langchain_leap0-0.2.0-py3-none-any.whl
Change of provenance
This file belongs to a release with changed provenance: the repository or configuration that created the release files differ from that of a previous release.
We recommend inspecting the repository and configuration before proceeding. View details.
| Download URL | langchain_leap0-0.2.0-py3-none-any.whl |
|---|---|
| Size | 8.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f4cc2c091560389b5eadb83675b7e4318a74745ae3a5b83798259077da7864d9
|
|
BLAKE2b-256 checksum How to use checksums |
5808f9e6335b18473d1892fd4aced03ea09fe420d1fe33fd47dcf55c50966b86
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Apr 12, 2026.
Transparency logSecurity for langchain-leap0 0.2.0
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.
Change of provenance
The repository that created this release differs from a previous release.
While this could reflect a routine change by the project maintainers, it may also indicate that the release files have been compromised.
Repository
- Removed 0.1.0 GitHub: leap0-dev/langchain-leap0
- Added 0.2.0 GitHub: leap0-dev/langchain-leap0-python
Attestation for langchain_leap0-0.2.0.tar.gz
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 Apr 12, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.