- Docker — Docker Desktop or Docker Engine
- A POSIX-Compatible System — Linux, macOS, WSL
-
containeris available as a NPM package. To install, simply run:npm install -g code-container
-
Run the following to copy all your AI harness configs from
~/to~/.code-container/configsfor mounting onto the container.container init
Alternatively, you can copy configs manually:
~/.config/opencode→~/.code-container/configs/.opencode~/.codex→~/.code-container/configs/.codex~/.copilot→~/.code-container/configs/.copilot~/.claude→~/.code-container/configs/.claude~/.claude.json→~/.code-container/configs/.claude.json~/.gemini→~/.code-container/configs/.gemini
-
Finally, build the Docker image. This may take up to 5 minutes.
container build
You're done 🎉; container is now ready to use.
Psst: Try my newest project: Nitro, a simple and efficient Bash harness. 11x cheaper; 75x more efficient vs Claude Code for simple Bash tasks.
npm install -g @aerovato/nitroNavigate to any project and run container to mount project and enter container.
cd /path/to/your/project
container # Enter containerInside the container: Start your harness and develop like normal.
opencode # Start OpenCode
npm install <package> # Persists per container
# ...Container state is saved. Next invocation resumes where you left off. AI conversations and settings persist across all projects.
container # Enter the container
container run /path/to # Enter container for specific project
container build # Build full Docker image (all stages)
container build packages # Rebuild from Packages stage
container build harness # Rebuild from Harness stage (update harnesses)
container build user # Rebuild User stage only (update your tooling)
container list # List all containers
container stop # Stop current project's container
container remove # Remove current project's container
container clean # Remove all stopped containers
container init # Copy/recopy config filesTip: Don't want to configure manually? Clone this repo and ask your harness to configure for you.
Please configure all my container harnesses to run without permissions. Add the following packages to the container environment: ... Add a custom mount point to the container environment: ...
Destructive actions are localized inside containers.
- You can let your harness run with full permissions
- To configure your harness to run without permissions, see
Permissions.md.
The image is built in 4 cascading stages:
- Core (packaged): Ubuntu 24.04, system dependencies, Node + NVM, Python
- Packages (customizable): Large user-specified packages & tooling
- Harness (packaged): OpenCode, Codex, Claude Code, etc.
- User (customizable): Small user-specified packages & setup scripts
FROM code-container-core:latest
RUN apt-get update && apt-get install -y postgresql-client redis-toolsFROM code-container-base:latest
RUN npm install -g bun typescript
RUN pip install requests
RUN npx opencode plugin opencode-quotes-plugin -gAfter modifying: Quickly rebuild use the appropriate build target:
container build packages # Rebuild from Packages stage
container build user # Rebuild from User stage only (very fast)Adding mount points: Edit ~/.code-container/MOUNTS.txt and reinitialize containers:
/absolute/path/on/host:/path/in/container
/absolute/path/on/host:/path/in/container:ro
Adding Docker flags:
Edit ~/.code-container/DOCKER_FLAGS.txt to pass additional flags to both docker run and docker exec:
# Environment variables
-e MY_VAR=value
For flags that only apply to docker run (e.g. port forwarding, network, GPU), use ~/.code-container/DOCKER_RUN_FLAGS.txt:
# Port forwarding
-p 4040:4040
-p 3000:3000
# GPU support
--gpus all
Each line is parsed like a shell command. Empty lines and lines starting with # are ignored.
You and multiple agents can work on the same project simultaneously.
- Safe: Reading files, editing files, most development operations
- Avoid: Simultaneous Git operations from both sides, installing conflicting
node_modules - Recommended Workflow: Let your harness run autonomously in the container while you work; review changes and commit.
- Changes within a container persists across sessions.
- Harness configurations and configuration histories are shared across containers.
containerprotects your host filesystem- Destructive operations will only affect the container
- Isolation prevents cross-contamination across containers
- Note: Git config and SSH keys are mounted read-only from host to support Git operations.
- Caution: Project files can still be deleted by harness; always use upstream version control
- Caution: Network access is still available; information may still be exfiltrated over network
- The main purpose of
containeris to protect commands likermoraptfrom unintentionally affecting your system. containerdoes not protect from prompt injections or network exfiltration in the event that your agent becomes malaligned.- Users are advised to not download or work with unverified software even within the container.
- Sensitive information inside the container may still be exfiltrated by an attacker just as with your regular system.
To uninstall container, uninstall the NPM package and remove ~/.code-container:
npm uninstall -g code-container
rm -rf ~/.code-containerConsider backing up the harness configurations in ~/.code-container/configs before removing.
