aicage
Run your favorite AI coding agents comfortably in Docker.
Why use aicage?
Agents need deep access (read code, run shells, install deps). Their built-in safety checks are naturally limited.
Running agents in containers gives a hard boundary - while the experience stays the same. See Why cage agents? for the full rationale.
Quick start
Install:
pipx install aicage
Use aicage in your IDE
Use your agent in your IDE, while aicage runs the agent in its Docker container.
See Use aicage in IDEs to connect IDE plugins to agents in aicage.
Set up a project
In your project directory, run:
aicage <agent>
For a first useful run, you can usually just press Enter or select OK when prompted.
-
Built-in agent examples:
aicage amp aicage auggie aicage claude aicage codex aicage copilot aicage droid aicage gemini aicage goose aicage kimi aicage kiro-cli aicage opencode aicage qwen aicage vibe
Your existing CLI config for each agent is mounted inside the container so you can keep using your preferences and credentials.
What you see first
After aicage <agent> starts, you will see this setup overview:
The overview brings the most common choices together in one place:
Agent: the built-in or custom agent you want to run.Bind Mounts: extra host files and directories the container should be able to access.Base: the base image used for the agent image. The suggested default is best for most users.Extensions: optional local additions that install tools or request extra host shares.Docker Args: extradocker runarguments such as-e,-p, or--network.Docker socket: lets the agent use Docker on the host when you explicitly enable it.OK: saves the current project config for that agent and starts the container.
Common next steps
Bind mounts
Use Bind Mounts when the agent needs access to files or directories outside the project.
Docker args
If you want to adjust how the container starts, open Docker Args in the setup screen.
Use it for normal docker run arguments such as:
-e FOO=bar
-p 3000:3000
--network my-net
See Docker run pass-through args.
Extensions
Extensions let you add tools on top of an existing agent image. Quick start:
git clone https://github.com/aicage/aicage-custom-samples.git $HOME/.aicage-custom
Then rerun aicage <agent> and select the extension in the setup screen.
See Extensions.
Docker socket access
If you want the agent to run Docker commands, enable Docker socket in the setup screen.
Full documentation
The complete user documentation lives in the wiki: aicage.wiki
For IDE setup, see Use aicage in IDEs.
Common scenarios
- Pass arguments to the agent:
aicage <agent> resume <session-id>
- Share additional host folders:
- Use
Sharesor extension-provided shares in the setup UI.
- Use
- Use proxies:
aicageforwardsHTTP_PROXY,HTTPS_PROXY,ALL_PROXY, andNO_PROXY.- See CLI options.
- Use host networking or custom networks:
- See Host networking.
- On Windows:
- set
git config --global core.autocrlf trueon the Windows host to avoid line-ending diffs.
- set
- On macOS with native Docker:
- See Known hiccups for the current support caveat.
- Run into first-use setup issues:
- See Known hiccups.
- Add custom tools/agents/base images:
Built-in agents
| CLI | Agent | Homepage |
|---|---|---|
| amp | Amp CLI | https://ampcode.com/docs/cli |
| auggie | Auggie CLI | https://docs.augmentcode.com/cli |
| claude | Claude Code | https://claude.com/product/claude-code |
| codex | Codex CLI | https://developers.openai.com/codex/cli |
| copilot | GitHub Copilot CLI | https://github.com/features/copilot/cli |
| droid | Factory CLI | https://factory.ai/product/cli |
| gemini | Gemini CLI | https://geminicli.com |
| goose | Goose CLI | https://goose-docs.ai |
| kimi | Kimi Code CLI | https://moonshotai.github.io/kimi-code |
| kiro-cli | Kiro CLI | https://kiro.dev/cli/ |
| opencode | OpenCode | https://opencode.ai |
| qwen | Qwen Code | https://qwenlm.github.io/qwen-code-docs |
| vibe | Mistral Vibe CLI | https://docs.mistral.ai/vibe/code/ |
Customization
aicage lets you customize images at three levels: extensions, agents, and base images. The sample repo is a fast
way to see working examples and copy a template.
Quick start:
git clone https://github.com/aicage/aicage-custom-samples.git $HOME/.aicage-custom
Then run any agent:
aicage <agent>
These are only samples. Use them to learn the structure, then replace or edit them with your own definitions.
aicage detects whatever you place under ~/.aicage-custom and offers it during selection.
Extensions can install tools and request additional host mounts.
After adding or changing custom definitions, restart aicage.
- Extensions: Customization-Extensions
- Custom agents: Customization-Agents
- Custom base images: Customization-Base-Images
Image updates are handled automatically; see Updates.
Why cage agents?
AI coding agents read your code, run shells, install packages, and edit files. That power is useful, but granting it directly on the host expands your risk surface.
Where built-in safety is limited:
- Allow/deny lists only cover known patterns; unexpected commands or attack paths can slip through.
- Some agents work fully only after relaxing their own safety modes, broadening what they can touch.
- “Read-only project” features are software rules. Other projects and files still sit alongside them on the same host.
How aicage mitigates this:
- Containers create a practical boundary: the agent can access only what you explicitly mount or share. Day-to-day use stays familiar while files you do not mount stay out of reach.
1 maintainer
Metadata
1 maintainer
Release files for aicage 1.5.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 | |
|---|---|---|---|---|
| aicage-1.5.0.tar.gz | 85.1 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| aicage-1.5.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 267.4 kB
Release files / aicage-1.5.0.tar.gz
| Download URL | aicage-1.5.0.tar.gz |
|---|---|
| Size | 85.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
809dff0112f7183ff03c1cc08b08d62484a48c9dc3ed65a32b710bc8ac7648be
|
|
BLAKE2b-256 checksum How to use checksums |
9319b1905cbdb3479a356f0cb5392017c18901cf698ec8019cdccf735f6fda0f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Oct 7, 2026.
Transparency logRelease files / aicage-1.5.0-py3-none-any.whl
| Download URL | aicage-1.5.0-py3-none-any.whl |
|---|---|
| Size | 182.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
28d4b78360364afdc23877330d17f4a4e977ff35b7ef68d418f3eedf1ca011a7
|
|
BLAKE2b-256 checksum How to use checksums |
a83ed5acb5b2cc2e41991d6afa95a3d2a0f909ceb3a4ea5d5d111bb4e34d9547
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Oct 7, 2026.
Transparency logSecurity for aicage 1.5.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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for aicage-1.5.0.tar.gz
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 Oct 7, 2026.
Transparency logA 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.
