Skip to main content

Agent Zoo

Agent Zoo

日本語 | English

CI

A security harness that isolates AI coding agents (Claude Code / Codex CLI / Gemini CLI) inside Docker containers and forces all outbound traffic through mitmproxy. Payload inspection plus TOML policy control physically prevent data exfiltration and dangerous command execution, without relying on the agent's own trustworthiness.

Quickstart

uv tool install agent-zoo                      # install from PyPI
mkdir my-zoo && cd my-zoo
zoo init                                       # secure by default: empty allow list (Inbox approval required)
# or: zoo init --policy claude                 # allow Anthropic/Claude only
# or: zoo init --policy {codex,gemini,all}     # see `zoo init --help`
zoo build                                      # build the claude image (5-10 min)
zoo run                                        # interactive mode (first run prompts /login)

zoo init now defaults to --policy minimal (empty domains.allow.list) so that the first outbound request is rejected and surfaced to the Inbox for per-request approval. Pick another profile (claude / codex / gemini / all) to preseed the allow-list, or edit .zoo/policy.toml directly. Live audit is available through the dashboard (zoo up --dashboard-only, http://localhost:8080).

Features

  • Docker isolation: agent containers run on an internal: true network, cut off from the host OS and other containers; the only egress is the mitmproxy sidecar
  • Domain allow-list: outbound destinations are explicitly enumerated in policy.toml, with hot reload support
  • Payload inspection: request and response bodies are inspected (Base64 decoding, secret patterns, URL-embedded secrets)
  • tool_use detection: SSE streams are parsed and dangerous tool invocations are blocked at the request hook
  • Dashboard auditing: requests / tool_uses / blocks shown live, with whitelist nurturing and Inbox (agent-to-human approval requests)
  • Agent-agnostic: same harness covers Claude Code / Codex CLI / Gemini CLI; the unified image enables cross-agent invocation

Documentation

Doc Contents
Install & Setup Detailed uv tool installzoo initzoo run flow, full command reference, unified profile
Inbox guide (JP) Approving agent-issued allow-list requests through the dashboard
Security model Defense in depth, known limitations, operating principles
Policy reference Every setting in policy.toml

License

MIT

Release files for agent-zoo 0.1.5

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for agent-zoo 0.1.5
File Size Uploaded
agent_zoo-0.1.5.tar.gz 1.4 MB Details

Built distribution (wheel)

Table of built distributions (wheels) for agent-zoo 0.1.5
File Interpreter ABI Platform
agent_zoo-0.1.5-py3-none-any.whl Python 3 none any Details

Total release size: 1.5 MB

Release files / agent_zoo-0.1.5.tar.gz

Download URL agent_zoo-0.1.5.tar.gz
Size 1.4 MB
Tags Source
SHA-256 checksum
How to use checksums
51eb4f84f77a4192810d959c04590cf1c9747eb6a1c1ba3ee2e7e702f7c595fa
BLAKE2b-256 checksum
How to use checksums
a3c98b22bf23c1e220d7403172e1eeee22fe399940b97c1bbf6684183aa8e615
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.13

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 Apr 20, 2026.

Transparency log

Release files / agent_zoo-0.1.5-py3-none-any.whl

Download URL agent_zoo-0.1.5-py3-none-any.whl
Size 98.7 kB
Tags Python 3
SHA-256 checksum
How to use checksums
2c9e8276c0f984769c4dd3424c0006b28810d2ab5ef557129b329879cc15be5e
BLAKE2b-256 checksum
How to use checksums
139c790d00180ddb7ebbd1a5eee991dff8c0a2db76e58d4efaaa16334a563c75
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.13

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 Apr 20, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

0.1.5 This release

2 release files

0.1.4

2 release files

0.1.3

2 release files

0.1.2

2 release files

0.1.1

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page