tai42-sandbox-local
A direct/host sandbox provider for the TAI ecosystem. It implements the
tai42_contract.sandbox.Sandbox surface over plain host subprocesses and the host
filesystem: it runs a session's code directly on the host, with no container
and no isolation. Exactly one sandbox provider is active per deployment, and the
operator picks direct/host execution by installing this provider instead of a
container provider — the consumers are provider-agnostic and acquire whichever is
installed.
The TAI ecosystem
TAI is an open-source runtime for MCP tools, agents, and workflows. A Sandbox is
"where a session's code runs" — a pluggable provider the runtime acquires through
one seam. This package is one such provider (direct/host execution); any package
can back the same contract, so this repo is this provider's own full doc home, and
the documentation site covers the platform-level story:
- Sandbox concept: https://tai42.ai/concepts/sandboxes
- Deployment / operate: https://tai42.ai/operate
Its only tai-* dependencies are tai42-contract (the Sandbox ABC, the session /
stream models, SandboxPolicy, the error family, PluginItemKind.SANDBOX, and the
tai42_app.sandboxes facet) and tai42-kit (ManagedSandbox /
ManagedSandboxSession — the shared ledger, TTL/reap, orphan recovery, and the
session-create policy chokepoint — plus SandboxDispatchSettings and the
conformance suite). It pulls in no third-party runtime dependency: it drives the
host with the standard library only.
Security model
This provider gives no isolation: isolation="none" means arbitrary session
code runs on the host with the host's filesystem, network, and secrets in reach.
It is for a trusted, single-tenant box, not untrusted flows. It accepts only
what it can honestly enforce and rejects the rest loudly:
isolation="none"accepted;container/vmrejected. The operator isolation floor defaults tocontainer, so a deployment installing this provider must setTAI_MCP_SANDBOX_ISOLATION=noneor every session create rejects.network="egress"accepted;none/internalrejected.- a
cpu/memory_mbcap rejected. imageis inert — the host is the execution environment; the operator installs the runtime on the host.
For enforced isolation or network lockdown, install a container provider instead.
Configuration
The SANDBOX_LOCAL_ env group: SANDBOX_LOCAL_ROOT (the host workspace root) and
SANDBOX_LOCAL_BASE_PATH (the clean-env PATH), plus the shared dispatch knobs
(SANDBOX_LOCAL_REAP_INTERVAL_SECONDS sets the platform reaper's sweep interval,
SANDBOX_LOCAL_EXEC_DEFAULT_TIMEOUT_SECONDS the timeout of a short exec that names
none). See
docs/index.mdx for the full table and
the durability model.
1 maintainer
Metadata
1 maintainer
Release files for tai42-sandbox-local 2.3.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| tai42_sandbox_local-2.3.0.tar.gz | 31.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| tai42_sandbox_local-2.3.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 53.3 kB
Release files / tai42_sandbox_local-2.3.0.tar.gz
| Download URL | tai42_sandbox_local-2.3.0.tar.gz |
|---|---|
| Size | 31.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
01a4541b65d994a1516245142f85a7df56693b2c17edce0469ea8d3d62271074
|
|
BLAKE2b-256 checksum How to use checksums |
f6fc62984c9d718c2d7eff35af6b65bf814b77f28b9633006d9fda02fe214b8d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Release files / tai42_sandbox_local-2.3.0-py3-none-any.whl
| Download URL | tai42_sandbox_local-2.3.0-py3-none-any.whl |
|---|---|
| Size | 21.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d27fde2b252475def27a5cc0df38b07be3bbda6448715a6cedd044f57eb00b02
|
|
BLAKE2b-256 checksum How to use checksums |
36b12872f89f0ad334a2378f8a501716906b4e68cc5faa3a59b755f07b682564
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Security for tai42-sandbox-local 2.3.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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A 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.
