Aicage — DevOps skill for Claude Code

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?](#why-cage-agents) for the full rationale.

Quick start

Install:

pipx install aicage

In your project directory, run:

aicage 

For a first useful run, you can usually just press Enter or select `OK` when prompted.

• Built-in agent examples:

  aicage agy
  aicage claude
  aicage codex
  aicage copilot
  aicage crush
  aicage droid
  aicage gemini
  aicage goose
  aicage opencode
  aicage qwen

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 ` 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: extra docker run arguments 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.

![