Clawk

*Give a coding agent its own disposable Linux machine, not yours.*

[](https://github.com/clawkwork/clawk/actions/workflows/ci.yml) [](LICENSE) [](go.mod) -lightgrey)

**[Install](#install)** · **[Quickstart](#quickstart)** · **[Why a VM?](#why-a-vm)** · **[How it works](#how-it-works)** · **[Compared to](#compared-to)** · **[FAQ](#faq)** · **[Docs](docs/)**

A coding agent is only useful when you let it actually *do* things: install packages, run the code it writes, start servers, use the network. On your own machine that leaves two bad options. You approve every command (and babysit a prompt every few seconds), or you run `--dangerously-skip-permissions` and hope nothing important is one `rm -rf` or one leaked token away.

clawk is a third option. `cd` into a repo, type `clawk`, and Claude Code (or Codex, or pi, or a shell) is working inside a disposable Linux VM (your code mounted in, root in the guest, no permission prompts) while your files, your keychain, and the rest of your machine stay out of reach. **The agent gets its own machine instead of yours.**

One command to a working agent; an attempt to send data to an unknown server, blocked by the network allow-list; clawk attach resumes the session later.

The bou