agno-opensandbox-toolkit
OpenSandbox support for the Agno agent framework.
Give your Agno agents the ability to execute shell commands, manage files, and run code in secure, isolated OpenSandbox containers.
Installation
# Base: shell commands + file operations
uv add agno-opensandbox-toolkit
# With code interpreter support (Python, JS, Java, Go, Bash)
uv add "agno-opensandbox-toolkit[code-interpreter]"
Prerequisites
You need a running OpenSandbox server. The quickest way:
uv pip install opensandbox-server
opensandbox-server init-config ~/.sandbox.toml --example docker
opensandbox-server
See the OpenSandbox docs for full setup instructions.
Quick Start
from agno.agent import Agent
from agno.models.openai import OpenAIChat
from agno_opensandbox_toolkit import OpenSandboxTools
agent = Agent(
name="Sandbox Agent",
model=OpenAIChat(id="gpt-4o-mini"),
tools=[OpenSandboxTools()],
markdown=True,
)
agent.print_response("Create a file /tmp/hello.py that prints 'Hello from OpenSandbox!', then run it")
Configuration
| Parameter | Env Variable | Default | Description |
|---|---|---|---|
domain |
OPENSANDBOX_DOMAIN |
localhost:8080 |
OpenSandbox server address |
api_key |
OPENSANDBOX_API_KEY |
"" |
API key for authentication |
protocol |
— | http |
Connection protocol (http or https) |
image |
— | ubuntu |
Container image |
timeout_minutes |
— | 10 |
Sandbox TTL |
sandbox_env |
— | {} |
Env vars inside sandbox |
sandbox_resources |
— | None |
e.g. {"cpu": "2", "memory": "4Gi"} |
sandbox_entrypoint |
— | None |
Custom entrypoint command list |
sandbox_metadata |
— | None |
Metadata labels dict |
enable_code_interpreter |
— | False |
Enable run_code tool |
persistent |
— | True |
Reuse sandbox across calls |
sandbox_id |
— | None |
Reconnect to existing sandbox |
Available Tools
| Tool | Description |
|---|---|
run_shell_command |
Execute bash commands |
create_file |
Create/update files |
read_file |
Read file content |
list_files |
List directory contents |
delete_file |
Delete files/directories |
change_directory |
Change working directory |
get_sandbox_status |
Get sandbox info |
shutdown_sandbox |
Kill the sandbox |
run_code |
Execute code via interpreter (optional) |
License
The project is published under the BSD 3-Clause license. For details see the LICENSE file.
Metadata
Release files for agno-opensandbox-toolkit 0.1.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 | Actions |
|---|---|---|---|---|
| agno_opensandbox_toolkit-0.1.0.tar.gz | 7.7 kB | Without provenance | Details for agno_opensandbox_toolkit-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| agno_opensandbox_toolkit-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for agno_opensandbox_toolkit-0.1.0-py3-none-any.whl |
Total release size: 16.8 kB
Release files / agno_opensandbox_toolkit-0.1.0.tar.gz
| Download URL | agno_opensandbox_toolkit-0.1.0.tar.gz |
|---|---|
| Size | 7.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1c3e0d2e9a4250689a5fcee419b679ece6e559cebeecef33232b1da7ce8c8cd9
|
|
BLAKE2b-256 checksum How to use checksums |
ed354ab23d432182a7087b518a59737eac3bbdfb8eb7948bbc3062fb97f09bf4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.7.22
|
Release files / agno_opensandbox_toolkit-0.1.0-py3-none-any.whl
| Download URL | agno_opensandbox_toolkit-0.1.0-py3-none-any.whl |
|---|---|
| Size | 9.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9cfabcc666f973edda05d1e1288b9079d91871ecfe5dd1866dda9ce4c404b5cd
|
|
BLAKE2b-256 checksum How to use checksums |
f96281f99eceee52f0e179e36798f6754ea1da589c634d7ad4e9017c18a4b42a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.7.22
|
Security for agno-opensandbox-toolkit 0.1.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.