A3S Box Python SDK
August 11, 2026 ยท View on GitHub
a3s-box is a local-first Python SDK with native Sandbox, commands, and
files APIs. It controls the A3S Box runtime installed on the same machine.
Local use
Install the A3S Box runtime and the Python package:
brew install a3s-lab/tap/a3s-box
python -m pip install a3s-box
No endpoint or API key is required:
from a3s_box import Sandbox
with Sandbox.create("python:3.12-alpine") as sandbox:
result = sandbox.commands.run("python -c 'print(6 * 7)'")
print(result.stdout)
sandbox.files.write("/workspace/note.txt", "hello")
print(sandbox.files.read("/workspace/note.txt"))
Export one bounded build or test artifact, optionally writing it to an exact host destination:
from a3s_box import Sandbox
with Sandbox.create("alpine:3.20") as sandbox:
artifact = sandbox.files.export(
"/workspace/report.json",
max_bytes=8 * 1024 * 1024,
destination="artifacts/report.json",
)
print(artifact.size, artifact.sha256)
The synchronous and asynchronous files.export() methods have a hard 8 MiB
ceiling. They check the file type and size before reading, reject declared-size
mismatches or stat/read size changes, and return the bytes with a lowercase SHA-256 digest. A
destination is created exclusively; an existing host file is never
overwritten.
Sandbox.create() defaults to alpine:3.20 and MicroVM isolation. The first
argument is an OCI image reference in local mode. Select the shared-kernel
Sandbox backend explicitly on a certified Linux host:
sandbox = Sandbox.create(
"python:3.12-alpine",
isolation="sandbox",
cpus=2,
memory_mb=1024,
)
By default, creation replaces the image command with a long-running keepalive
process. Set command and entrypoint to configure the initial OCI process,
including on Windows/WHPX where post-boot command execution is unavailable:
sandbox = Sandbox.create(
"alpine:3.20",
entrypoint=["/bin/sh", "-c"],
command=["echo ready; exec httpd -f -p 8080"],
)
Async applications use the same local runtime:
import asyncio
from a3s_box import AsyncSandbox
async def main() -> None:
async with await AsyncSandbox.create("python:3.12-alpine") as sandbox:
result = await sandbox.commands.run(["python", "-c", "print(6 * 7)"])
print(result.stdout)
asyncio.run(main())
Lifecycle and inspection
Local Sandbox lifecycle calls are generation-fenced. stop() preserves the
durable Sandbox, restart() advances its generation under a caller-supplied
idempotency identity, remove() deletes a terminal Sandbox, and kill()
performs stop plus removal. Reuse the same operation_id when retrying a
restart whose outcome is not yet known.
from a3s_box import A3SBoxClient, ExecutionResourceUpdate, Sandbox
client = A3SBoxClient()
sandbox = Sandbox.create("alpine:3.20")
try:
logs = sandbox.logs(tail=100)
stats = sandbox.stats()
print(len(logs), stats.memory_percent if stats else None)
processes = sandbox.processes()
runtime_stats = sandbox.runtime_stats()
events = sandbox.events(
after_sequence=0,
limit=256,
wait_timeout_ms=1_000,
)
event_stream = sandbox.stream_events(after_sequence=events.next_sequence)
print(len(processes.processes), runtime_stats.memory.usage_bytes)
print(events.next_sequence)
sandbox.update_resources(
ExecutionResourceUpdate(cpu_shares=512),
operation_id="ci-resources-1",
)
print(next(event_stream).kind)
event_stream.close()
sandbox.stop()
sandbox.restart(operation_id="ci-restart-1", stop_timeout=10)
print(client.get_sandbox(sandbox.id))
finally:
sandbox.kill()
Log snapshots contain structured stream, message, and timestamp values, and
accept tails from 1 through 10,000 entries. The runtime client also exposes
list_sandboxes(), get_sandbox(), runtime_diagnostics(),
runtime_disk_usage(), list_filesystem_snapshots(), and
get_filesystem_snapshot(). A3SAsyncBoxClient and AsyncSandbox provide
the same operations with async methods.
processes(), runtime_stats(), events(), and stream_events() accept a
running or paused Sandbox and preserve its exact generation;
update_resources() requires a running Sandbox. Event polls and stream batches
default to 256 items and accept at most 4,096. A synchronous stream can use a
threading.Event for bounded cross-thread cancellation. AsyncSandbox returns
an async iterator whose task cancellation kills the active local bridge
process. Streams terminate on generation drift instead of following a restart.
Reuse an explicit resource-update operation_id when retrying an outcome that
is not yet known.
Builder-style programmable CI/CD
The direct Sandbox API remains available for execution. For build and CI
tooling, A3SBoxClient adds fluent builders over the same local runtime and
bridge:
from a3s_box import A3SBoxClient
client = A3SBoxClient()
image = (
client.image("./ci")
.dockerfile("Dockerfile")
.tag("local/ci-base:latest")
.build_arg("NODE_VERSION", "24")
.build()
)
cache = (
client.volume("npm-cache")
.label("purpose", "ci-cache")
.size_limit(10 * 1024 * 1024 * 1024)
.create()
)
network = client.network("ci-net").subnet("10.89.40.0/24").create()
with (
client.sandbox(image.reference)
.cpus(4)
.memory_mb(4096)
.entrypoint("/usr/bin/env", "sh")
.command("-c", "npm test && sleep 3600")
.mount_named(cache.name, "/root/.npm")
.network(network.name)
.publish_tcp(8080, 8080)
.workdir("/workspace")
.start()
) as box:
result = (
box.script("npm ci\nnpm test\n")
.interpreter("/bin/sh", "-se")
.env("CI", "true")
.run()
)
if result.exit_code != 0:
raise RuntimeError(result.stderr)
A3SAsyncBoxClient provides the same builders with asynchronous terminal
operations. Named volumes and networks must be created explicitly before they
are mounted or selected. Builder scripts are sent through standard input to
the selected interpreter, so their contents are not interpolated into a host
shell command. Initial command and entrypoint argument vectors are validated
before the runtime is invoked.
Named bridge networks and published ports are currently MicroVM-only. A
shared-kernel Sandbox request that selects either fails before runtime
mutation; use .disable_network() or the default TSI-compatible configuration
for supported Sandbox workloads.
The package invokes the versioned machine bridge built into the installed
a3s-box executable. It does not parse human CLI output. Protocol v3 performs
one shared, complete capability handshake before the first normal operation,
including when callers start concurrently. Typed response fields and standard
Base64 are validated fail-closed; malformed responses use
bridge_protocol_error, a missing binary uses binary_not_found, and a local
bridge deadline uses bridge_timeout. Set A3S_BOX_BINARY only when the
executable is not on PATH.
Host resources use the same typed client:
import os
from a3s_box import A3SBoxClient, RegistryCredentials, SignaturePolicy
client = A3SBoxClient()
credentials = RegistryCredentials("builder", os.environ["REGISTRY_PASSWORD"])
image = client.pull_image(
"registry.example/ci/base:latest",
credentials=credentials,
signature_policy=SignaturePolicy.cosign_key("/keys/cosign.pub"),
)
metadata = client.inspect_image(image.reference)
history = client.image_history(image.reference)
tagged = client.tag_image(image.reference, "local/ci-base:tested")
client.push_image(
tagged.reference,
"registry.example/ci/base:tested",
credentials=credentials,
)
client.prune_volumes()
client.prune_networks()
client.capabilities() returns bridge protocol version 3 and the exact 52
supported operation names. Registry passwords are passed only to the local
runtime process.