clawker CLI
A CLI that runs Claude Code and Codex in isolated Docker containers with a firewall, worktrees and a no-Dockerfile image.
- 59 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- Installs a control container with eBPF and a firewall, carries host settings and skills into the container and runs the agent with broad permissions inside it.
Install
- Works in
Manual install
brew install schmitthub/tap/clawkerFor macOS; macOS and Linux also have an install script, and a Go source build exists.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Installs a control container with eBPF and a firewall, carries host settings and skills into the container and runs the agent with broad permissions inside it.
This is third-party code. Review the repository files before installing.
What it does
clawker builds a project image on Debian with a toolset (git, curl, ripgrep, zsh), language stacks (Go, Node, Python, Rust, Java, Ruby, C++, .NET) and your build commands, then runs the agent inside. Claude Code and Codex ship as built-in bundles, and any other agent CLI harness is added with your own bundle. The container gets the repository working copy through a directory bind or a snapshot. A control container on the host manages the firewall, the lifetime of eBPF programs and the agent registry, while in each container a `clawkerd` daemon acts as PID 1, drops privileges and supervises the agent. Host settings, plugins and skills are carried into the container. `clawker go dev` combines launching, and `clawker monitor` enables logs and metrics.
Who it is for. Developers and teams who run agents with broad permissions and want them in an isolated container with network restrictions.
Good fit when
- The agent runs commands without confirmations and they must be contained.
- Several agents work on a project in parallel across different worktrees.
- You need container logs and metrics to analyze agent behavior.
- An unfamiliar repository is being tested and the host must not run its scripts directly.
Not a fit when
- Docker is not installed on the machine.
- Work happens on Windows: the platform is not supported yet.
- You need protection from compromise of Docker itself or the host kernel.
Example request
Build an image for this project and start Claude Code in a container with the repository working copy.Limitations
A working Docker is required. The author tested features on macOS, Linux is confirmed but not extensively, and Windows is not supported. Building from source needs Go 1.27.1 or newer. On first run the agent sign-in happens inside the container and persists in the agent config volume. A container isolates files and network but does not replace other protections, and the `curl` installer runs a script worth reading before execution.
How to disable. Remove containers and images with clawker commands, then the app itself: `brew uninstall clawker` or delete the binary from the install directory.
FAQ
How do I install clawker?
On macOS with `brew install schmitthub/tap/clawker`. On macOS and Linux the install script `curl -fsSL https://raw.githubusercontent.com/schmitthub/clawker/main/scripts/install.sh | bash` works. Docker must be installed.
How do I start an agent?
In the project run `clawker init`, `clawker build` and `clawker go dev`. The `go` alias expands to `clawker run --rm -it --agent dev @`.
How do I pick Codex instead of Claude Code?
Use `@:codex` instead of `@`: it selects the image for that agent harness.
What do bind and snapshot modes do?
Bind mounts the repository into the container while snapshot copies it. The choice decides whether agent changes land in the working copy right away.
How do I enable monitoring?
Run `clawker monitor init` and `clawker monitor up` before starting agents: container logs and metrics appear.
Discussion
No questions or reviews yet.
Related
CLI toolsclawk is a virtual-environment CLI that snapshots a Linux machine’s memory and disk so running processes can be resumed later.
Brig runs Claude Code and other coding agents inside an isolated microVM on your machine with access to one project only.
A Docker sandbox for coding agents: a Debian image with Copilot CLI, Codex and Pi, and SSH, RDP and Docker enabled by flags.
ClaudeBox runs Claude Code in Docker with language profiles, session slots and a firewall with an allowlist of addresses.
ExitBox runs Claude, Codex, Cursor and other agents in rootless containers: a domain allowlist and secrets in an encrypted vault.
A container for Claude Code, Codex, Copilot, OpenCode and Pi: the agent runs without prompts while a gateway limits network.
README in short
The author describes clawker as a free self-hosted sandbox for coding agents: multi-harness, with Dockerfile-free images, a firewall and observability. Guides cover containers, worktrees, aliases and resources.