langchain-islo
Islo sandbox integration for Deep Agents.
Islo provides long-running, reconnect-surviving AI sandboxes on real Linux VMs, with pause/resume, snapshots, and a gateway layer for secret isolation and egress policies.
Install
uv add langchain-islo
# or: pip install langchain-islo
Set your API key (keys look like ak_...):
export ISLO_API_KEY="ak_..."
Sandbox image requirement. The inherited filesystem tools (
read,write,edit,ls,glob,grep) shell out topython3and GNUgrepinside the sandbox. Use an image that provides them (e.g.python:3.12-slim, orubuntu/debianwithpython3+grepinstalled). Alpine/BusyBoxgreplacks the flags these tools need.
Usage
Wrap an existing Islo sandbox and use it as a Deep Agents backend:
from islo import Islo
from langchain_islo import IsloSandbox
client = Islo() # reads ISLO_API_KEY
sandbox = client.sandboxes.create_sandbox(image="python:3.12-slim")
backend = IsloSandbox(client=client, sandbox=sandbox)
result = backend.execute("echo hello")
print(result.output) # "hello"
# Filesystem tools are inherited from BaseSandbox:
backend.write("/workspace/app.py", "print('hi')\n")
print(backend.read("/workspace/app.py").file_data["content"])
Lifecycle helper
IsloProvider creates, attaches to, and deletes sandboxes for you:
from langchain_islo import IsloProvider
provider = IsloProvider() # reads ISLO_API_KEY
backend = provider.get_or_create(image="python:3.12-slim")
try:
print(backend.execute("uname -a").output)
finally:
provider.delete(sandbox_id=backend.id)
What you get
IsloSandbox subclasses deepagents.backends.sandbox.BaseSandbox, so it
implements the full SandboxBackendProtocol:
| Method | Backed by |
|---|---|
execute() |
Islo exec_in_sandbox + result polling (commands run via sh -c) |
upload_files() / download_files() |
Islo sandbox files endpoint (raw bytes) |
ls / read / write / edit / glob / grep |
Inherited from BaseSandbox |
id |
Islo sandbox id |
Async variants (aexecute, aupload_files, adownload_files, ...) are provided
by the base class via thread offloading.
Configuration
| Env var | Default | Purpose |
|---|---|---|
ISLO_API_KEY |
— | Bearer token used to authenticate |
ISLO_BASE_URL |
https://api.islo.dev |
Control-plane base URL |
License
MIT
Release files for langchain-islo 0.0.4
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_islo-0.0.4.tar.gz | 148.7 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| langchain_islo-0.0.4-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 158.9 kB
Release files / langchain_islo-0.0.4.tar.gz
| Download URL | langchain_islo-0.0.4.tar.gz |
|---|---|
| Size | 148.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d1674de7c1d547d8601ce9897ec23ca158cf46befc01ddddd16bc6cdb1c2e13e
|
|
BLAKE2b-256 checksum How to use checksums |
538c51efded613d511c1ab27a3941c1ba9564f443d55b4d2481d8fa4db3b24bb
|
| 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 Jun 7, 2026.
Transparency logRelease files / langchain_islo-0.0.4-py3-none-any.whl
| Download URL | langchain_islo-0.0.4-py3-none-any.whl |
|---|---|
| Size | 10.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
807188bc183f8ed93f6f20e6c90e6c64e4032fd256071f7e79d06a0abc4483d8
|
|
BLAKE2b-256 checksum How to use checksums |
812ea78ce6d2d85bcbabb79d35e37cdb03b30fc397bb0e2266f1b6d93f772776
|
| 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 Jun 7, 2026.
Transparency log