claudeers.

🔓 unclaimed — this page was auto-generated from GitHub. Are you the creator?

Claim this page →
// Claude Skills

container

Safely run OpenCode, Codex, Claude Code with full permissions.

Actively maintained
100/100
last commit 3 days ago
last release 3 days ago
releases 24
open issues 0
// install
git clone https://github.com/aerovato/container

Banner

container: Isolated Docker environments for your autonomous coding harnesses.

Simple. Lightweight. Secure.

Quickstart

Prerequisites

  • A Windows, Mac, or Linux machine (Both Windows native and WSL are now supported!)
  • Docker or Podman — Docker Desktop/Engine or Podman

Installation

  1. container is available as an NPM package. Install with:

    npm uninstall -g code-container      # Uninstall V2 if present
    npm install -g @aerovato/container   # Install container V3
    
  2. Run container init (interactive onboarding). It will:

    • Detect installed harnesses (Claude Code, OpenCode, etc.)
    • Migrate your existing configs
    • Let you choose Docker or Podman
    • Configure SSH and git mounts

    Accept the prompt to build the image (first build can take 5+ minutes).

You're done. container is ready to use.

Shameless Self-Promotion

Try Nitro, a simple and efficient Bash harness. 11x cheaper, 75x more efficient than Claude Code for simple Bash tasks.

npm install -g @aerovato/nitro

Usage

Navigate to any project and run container:

cd /path/to/your/project
container

Inside the container: Start your harness and develop like normal.

opencode                     # Start OpenCode
npm install <package>        # Persists per container
# ...

Your project is mounted at /root/<project-name>. Changes persist across sessions. Harness configs are shared across all containers.


You may want to periodically rebuild the image to update harnesses and packages:

container build               # Trigger full rebuild
container build harness       # Rebuild harnesses and user packages
container build user          # Rebuild user packages

Common Commands

container                           # Enter container for current directory
container run /path/to/project      # Enter for a specific project
container run /path -- -p 8080:80   # Pass extra runtime flags
container list                      # List all containers
container stop                      # Stop container
container remove                    # Remove container
container init                      # Re-run onboarding

Customization

Customization is done through two places:

1. ~/.code-container/Dockerfile.User

Add packages and setup steps here. Example:

FROM localhost/aerovato/container-v3-harness:latest

RUN npm install -g bun typescript
RUN pip install requests

RUN npx opencode plugin opencode-quotes-plugin -g

After editing, run container build user to rebuild the image

2. ~/.code-container/settings.json

Primary configuration file. See docs/Settings.md for more details.

Common settings:

  • enabledHarnesses — which harnesses to install
  • runtime"docker" or "podman"
  • dockerfileCore — advanced control over the base image
  • systemMounts — gitconfig and SSH mounts
  • dockerRunFlags / dockerExecFlags — extra runtime flags

Hint: Clone this repo and ask your agent to configure for you.

For V2 Users

After upgrading to V3, all configurations will be archived to ~/.code-container/archive. To migrate configurations over, ask your agent to read and perform the steps in docs/Migration.md.

Features

  • Isolation — Destructive actions stay inside the container
  • 3-Stage Builds — Core → Harness → User (rebuild only what changed)
  • Configurable Runtime — Docker or Podman
  • Cross-Platform — Linux, macOS, Windows (both native and WSL)
  • Harness Packs — Choose exactly which tools to enable
  • Persistent State — Workspaces and configs survive across sessions
  • Simultaneous Work — Multiple agents can safely work on the same project

Security

  • container protects your host filesystem from rm -rfs
  • Packages and configurations inside containers stay localized
  • Isolation prevents cross-contamination across containers

Important limitations:

  • container does not protect against prompt injection or agent misalignment
  • Network access is available inside the container
  • Harness configs will be mounted inside container

Uninstall

npm uninstall -g @aerovato/container
rm -rf ~/.code-container

Consider backing up the harness configurations in ~/.code-container/configs before removing.

// compatibility

Platformscli, desktop
Operating systems
AI compatibilityclaude
LicenseBSD-3-Clause
Pricingopen-source
LanguageTypeScript

// faq

What is container?

Safely run OpenCode, Codex, Claude Code with full permissions.. It is open-source on GitHub.

Is container free to use?

container is open-source under the BSD-3-Clause license, so it is free to use.

What category does container belong to?

container is listed under devops in the Claudeers registry of Claude-compatible tools.

0 views
300 stars
unclaimed
updated 15 days ago

// embed badge

container on Claudeers
[![Claudeers](https://claudeers.com/api/badge/container.svg)](https://claudeers.com/container)

// retro hit counter

container hit counter
[![Hits](https://claudeers.com/api/counter/container.svg)](https://claudeers.com/container)

// reviews

// guestbook

0/500

// related in Claude Skills

🔓

An agentic skills framework & software development methodology that works.

// skillsobra/Shell249,840MIT[ claude ]
🔓

💫 Toolkit to help you get started with Spec-Driven Development

// skillsgithub/Python117,790MIT[ claude ]
🔓

Public repository for Agent Skills

// skillsanthropics/Python159,495[ claude ]
🔓

AI coding assistant skill (Claude Code, Codex, OpenCode, Cursor, Gemini CLI, and more). Turn any folder of code, SQL schemas, R scripts, shell scripts, docs,…

// skillsGraphify-Labs/Python77,228MIT[ claude ]
Ecosystem hubone of the most connected projects in the claude ecosystem · 18 connections
→ see how container connects across the ecosystem