bilrost
Harness isolation for AI agents, in a Lima VM — overlay isolation, network containment, secrets management, and gated sync.
Status: deprecated. Bilrost is no longer in active use and remains available as a research artifact. It provides harness isolation for experiments and is not a hardened security product. Releases are not signed with PyPI attestations, and CI is maintained on a best-effort basis.
Install
# Via pipx (recommended)
pipx install bilrost
# Via uv
uv tool install bilrost
# Via pip
pip install bilrost
Usage
# Interactive setup
bilrost init
# Provision the VM (~5 min first run)
bilrost up
# Check status
bilrost status
# SSH into the VM
bilrost ssh
# Sync overlay changes to host (with secret scanning)
bilrost sync
# Stop / destroy
bilrost down
bilrost destroy
MCP Server
Agents can manage the sandbox programmatically via FastMCP:
{
"mcpServers": {
"sandbox": {
"command": "bilrost-mcp"
}
}
}
9 tools: sandbox_status, sandbox_up, sandbox_down, sandbox_destroy, sandbox_exec, sandbox_validate, sandbox_ssh_info, sandbox_gateway_info, sandbox_agent_identity.
What It Does
- OverlayFS isolation — host code mounted read-only, all writes contained in VM overlay
- Network containment — UFW firewall with explicit allowlist (HTTPS, DNS, Tailscale, NTP only)
- Secrets management — three injection methods,
0600perms, never in process lists - Gated sync — gitleaks scanning + path allowlist before changes reach your host
- Docker sandboxing — per-session containers with configurable network isolation
- 12 Ansible roles — overlay, secrets, gateway, docker, firewall, sync-gate, gh-cli, buildlog, cadence, qortex, tailscale, and more
Requirements
- macOS (Apple Silicon or Intel)
- Homebrew
- ~10GB disk space
Dependencies (Lima, Ansible, etc.) are installed automatically on first run.
Documentation
Full docs: peleke.github.io/openclaw-sandbox
License
MIT
Metadata
Release files for bilrost 1.3.2
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 |
|---|---|---|---|---|
| bilrost-1.3.2.tar.gz | 24.3 kB | Without provenance | Details for bilrost-1.3.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| bilrost-1.3.2-py3-none-any.whl | Python 3 | none | any | Details for bilrost-1.3.2-py3-none-any.whl |
Total release size: 56.2 kB
Release files / bilrost-1.3.2.tar.gz
| Download URL | bilrost-1.3.2.tar.gz |
|---|---|
| Size | 24.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
95a0646a5cf0c6e279025a325225fc24159e67ea3353b433c7eaeb0af47d98b1
|
|
BLAKE2b-256 checksum How to use checksums |
c090fec19aa791a8f9e061a37ab17d18e5f717d5f5016a9f346b2ff710c92177
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Release files / bilrost-1.3.2-py3-none-any.whl
| Download URL | bilrost-1.3.2-py3-none-any.whl |
|---|---|
| Size | 31.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
14d451c07c543824c7da039c3f9f690056810e5ca42b32d4c9a56f40b212dc70
|
|
BLAKE2b-256 checksum How to use checksums |
463c16b499d5af6abed83fe6cb26740f3c6f2f35f484559d13eac3268114e55a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Security for bilrost 1.3.2
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.