clawk and Sculptor both run AI coding agents in isolated environments on your own machine. Here is how their sandboxing models, platforms, and setup differ.
Searching for "clawk vs Sculptor" usually means you want to let an AI coding agent install packages, run code, and touch the network without handing it your laptop. Both tools answer that, and both are open source, run locally, and support Apple silicon. They take different routes to the same goal.
clawk gives a single agent its own disposable Linux virtual machine per project, with your code mounted in and outbound network traffic filtered by an allow-list. Sculptor runs multiple coding agents in parallel, each in its own isolated git worktree. This comparison lays out what each one does, what platforms and licenses they carry, and which workflow each fits, using the projects' own pages as of 2026-08-08.
At a glance
In short
Both are free, open-source, local-first sandboxes for AI coding agents that run on Apple silicon, and they solve different problems. Pick clawk if you want one agent to own a disposable Linux VM it can fully reconfigure, with an outbound network allow-list, on macOS 14+ Apple silicon (Apache-2.0). Pick Sculptor if you want to run several coding agents in parallel, each in an isolated git worktree, on Mac or Linux, and you already have a paid Claude plan (MIT). All figures as of 2026-08-08.
Head to head
Key differences side by side; the stronger option is tinted green.
| Feature | clawk | Sculptor |
|---|---|---|
| Isolation model | Disposable Linux VM per project with a separate kernel; code mounted in, root in the guest (README, 2026-08-08) | Isolated git worktree per agent for parallel work (product page, 2026-08-08) |
| Primary use case | Give one coding agent its own machine to fully reconfigure | Run multiple coding agents in parallel |
| License | Apache-2.0 (README, 2026-08-08) | MIT (product page, 2026-08-08) |
| Platforms | macOS 14+ on Apple silicon; Linux via firecracker is experimental; no Windows (README, 2026-08-08) | Mac Apple silicon and Linux; no Windows (product page, 2026-08-08) |
| Linux support | Experimental via firecracker (README, 2026-08-08) | Supported (product page, 2026-08-08) |
| Agent runners | Claude Code, Codex, or a plain shell (README, 2026-08-08) | Requires an existing paid Claude plan (product page, 2026-08-08) |
| Outbound network control | DNS-aware egress allow-list; unknown servers blocked, github.com pre-allowed (README, 2026-08-08) | Not covered on the pages we read (2026-08-08) |
| Data locality | Local-first; code never leaves the machine, nothing billed by the hour (README, 2026-08-08) | Local-first; data stays on your machine (product page, 2026-08-08) |
| Cost to obtain | Free, open source (README, 2026-08-08) | Free, open source, but requires a paid Claude plan to use (product page, 2026-08-08) |
Feature matrix
| Feature | clawk | Sculptor |
|---|---|---|
| Open source — Apache-2.0 (clawk); MIT (Sculptor), as of 2026-08-08 | ✅ | ✅ |
| macOS Apple silicon — clawk requires macOS 14+, as of 2026-08-08 | ✅ | ✅ |
| Linux support — clawk's firecracker provider is experimental, as of 2026-08-08 | 🟡 | ✅ |
| Windows support — Neither page listed Windows support, as of 2026-08-08 | ❌ | ❌ |
| Local-first (data stays on your machine) | ✅ | ✅ |
| Requires a paid Claude plan to use — clawk can attach a plain shell, Codex, or Claude Code; Sculptor requires a paid Claude plan, as of 2026-08-08 | ❌ | ✅ |
✅ full · 🟡 partial/paid · ❌ not supported
Pricing
Confirm current pricing on each vendor's site.
clawkFree, open source (Apache-2.0), as of 2026-08-08
Disposable Linux VM per project on macOS 14+ Apple silicon
Attach Claude Code, Codex, or a plain shell
DNS-aware outbound allow-list; host filesystem and keychain out of reach
Installs via Homebrew; no Docker, qemu, or sudo required
Local-first, nothing billed by the hour
View clawk on GitHubSculptorFree, open source (MIT); requires an existing paid Claude plan, as of 2026-08-08
Runs coding agents in parallel, each in an isolated git worktree
Mac Apple silicon and Linux
Local-first: data stays on your machine
Driven by your existing paid Claude plan
Pros & cons
clawkPros
Machine-level isolation: separate kernel, host filesystem never mounted (README, 2026-08-08)
Outbound traffic held to a DNS-aware allow-list (README, 2026-08-08)
Root in the guest lets an agent install packages and run privileged services
Works with Claude Code, Codex, or a plain shell (README, 2026-08-08)
No Docker, qemu, or sudo needed to run it (README, 2026-08-08)
Cons
Requires macOS 14+ on Apple silicon; Linux support is experimental (README, 2026-08-08)
Pre-1.0 with breaking changes expected between releases (README, 2026-08-08)
No Windows or Intel Mac support (README, 2026-08-08)
SculptorPros
Runs multiple agents in parallel, each in its own worktree (product page, 2026-08-08)
Runs on both Mac Apple silicon and Linux (product page, 2026-08-08)
Local-first: data stays on your machine (product page, 2026-08-08)
MIT-licensed and free to obtain (product page, 2026-08-08)
Cons
Requires an existing paid Claude plan to use (product page, 2026-08-08)
No Windows support (product page, 2026-08-08)
Clawk and Sculptor: the public release record on 2026-08-08
| Measured on 2026-08-08 | Clawk clawkwork/clawk | Sculptor imbue-ai/sculptor |
|---|---|---|
| Latest release | v0.3.0, published 2026-08-05 | sculptor-v0.44.0rc2, published 2026-08-07 |
| Commits, weekly average | 2.5 a week (30 commits in the 12 weeks to 2026-08-08) | 151.6 a week (1,819 commits in the 12 weeks to 2026-08-08) |
| Most recent commit | 2026-08-05 | 2026-08-07 |
According to figures this site recorded on 2026-08-08 from each project's public source repository on GitHub, Clawk (clawkwork/clawk) averaged 2.5 commits a week over the preceding 12 weeks, while Sculptor (imbue-ai/sculptor) averaged 151.6 commits a week over the same span. Both numbers are drawn from the repositories' public commit histories, not from a package registry or any vendor's status page, so they measure recorded development activity and nothing more. For someone choosing between the two tools, the gap reasonably suggests that Sculptor is under far more frequent active development, which may matter if steady updates and quick fixes are a priority. What the figures do not establish is how reliable either tool is, what support a user can expect, the quality of the finished product, or how many people actually use it. A busy commit log signals effort, not outcomes, and should be weighed alongside evidence the raw counts cannot supply.
Where these numbers come from: on 2026-08-08 (2026-08-08T00:05:48Z) we called the public endpoints listed below and recorded what they returned. Nothing here is taken from either vendor's marketing pages, and anyone can repeat the same calls. Repository figures describe the named repository — for a closed-source platform that is its official CLI or SDK, not the platform itself. What these figures do not tell you: Commit counts include merges, dependency bumps and documentation changes, and a monorepo will always show more commits than a single-purpose repository, so this measures how busy the named repository is — not progress, quality, or how much of it reaches the product. The commit date says the repository is being worked on, nothing about what changed. None of them measures reliability, support or how either product feels to use.
Clawk — GitHub REST API · GitHub releases API · the project's own repository, where its releases are published
Sculptor — GitHub REST API · GitHub releases API · Imbue's own repository for the project
What clawk does
clawk hands a coding agent a disposable Linux VM instead of your host machine. You cd into a repository, type clawk, and Claude Code (or Codex, or a plain shell) starts working inside a fresh Linux VM with your code mounted in and root access in the guest, so there are no per-command permission prompts (clawk GitHub README, as of 2026-08-08).
The isolation is structural rather than a set of rules the agent could be argued out of. The guest runs its own Linux kernel, so the host filesystem is never mounted into it, and outbound connections pass through a DNS-aware allow-list that blocks servers you have not permitted; github.com is pre-allowed and the host's ssh-agent is forwarded so git push still works while your keys stay on the host (clawk GitHub README, as of 2026-08-08).
The hypervisor is Apple's Virtualization.framework, linked into the binary, so no Docker, qemu, or sudo is required to run it. A clawk.mod file, written in a go.mod-style syntax, lets a project declare CPU, memory, the OCI image used as the rootfs, allowed hosts, port forwards, and environment variables. clawk attach resumes a session, and a ticket mode manages worktrees and PRs (clawk GitHub README, as of 2026-08-08).
What Sculptor does
Sculptor, from Imbue, runs coding agents in parallel, each inside its own isolated git worktree, so several agents can work at once without stepping on each other's changes (Imbue Sculptor product page, as of 2026-08-08).
It is local-first: the product page describes your data staying on your machine rather than being sent to a hosted service. Using Sculptor requires an existing paid Claude plan, which it drives to power the agents (Imbue Sculptor product page, as of 2026-08-08).
The worktree model is the differentiator here. Where clawk centers on one agent owning one whole VM, Sculptor's emphasis is on running many agents side by side, each with an isolated copy of the working tree, so you can spin up several attempts or tasks concurrently and compare results (Imbue Sculptor product page, as of 2026-08-08).
How the two isolation models differ
The core distinction is the unit of isolation. clawk isolates at the machine level: a separate Linux kernel and userland the agent can fully reconfigure, with the host filesystem simply absent rather than hidden behind deny rules (clawk GitHub README, as of 2026-08-08). Sculptor isolates at the worktree level: separate checkouts of your repository so parallel agents do not collide (Imbue Sculptor product page, as of 2026-08-08).
That difference shapes what each is good at. A full VM lets an agent install system packages, edit /etc, bind privileged ports, and (on supported hardware, opt-in) run Docker or Kubernetes workflows inside the sandbox (clawk GitHub README, as of 2026-08-08). Worktree isolation is lighter and geared toward running many agents at once on the same codebase.
clawk also documents an outbound network allow-list as a first-class boundary (clawk GitHub README, as of 2026-08-08). Sculptor's network handling was not covered on the pages we read on 2026-08-08, so we do not score that dimension for it.
Platforms, licensing and cost
Both are open source and free to obtain. clawk is licensed under Apache-2.0; Sculptor is licensed under MIT (clawk GitHub README and Imbue Sculptor product page, both as of 2026-08-08).
Platform support is where they part. clawk requires macOS 14 or later on Apple silicon; its Linux provider uses firecracker and is described as experimental, and there is no Windows or Intel Mac support (clawk GitHub README, as of 2026-08-08). Sculptor runs on Mac Apple silicon and Linux, with no Windows support (Imbue Sculptor product page, as of 2026-08-08).
On cost, neither charges for the software itself. The practical difference is that Sculptor requires an existing paid Claude plan to use (Imbue Sculptor product page, as of 2026-08-08), whereas clawk lets you attach Claude Code, Codex, or a plain shell, so a bare shell needs no agent subscription at all (clawk GitHub README, as of 2026-08-08). clawk is local-first with nothing billed by the hour, and Sculptor keeps your data on your machine (both pages, as of 2026-08-08).
One caveat on maturity: clawk describes itself as pre-1.0 and under active development, with breaking changes expected between releases (clawk GitHub README, as of 2026-08-08).
Which one fits your workflow
Because they target different workflows, several rows in the comparison have no single winner. Pick by the question you are trying to answer.
Choose clawk when you want one agent to have a whole disposable machine it can reconfigure — installing system packages, running privileged services, or (on supported hardware) Docker and Kubernetes inside the sandbox — with outbound traffic held to an allow-list and your host filesystem and keychain out of reach (clawk GitHub README, as of 2026-08-08). It suits a security-conscious solo workflow on Apple silicon.
Choose Sculptor when the bottleneck is throughput rather than machine-level isolation: running several coding agents at once, each in its own worktree, on a Mac or Linux box, and you already pay for a Claude plan (Imbue Sculptor product page, as of 2026-08-08).
Verdict
clawk and Sculptor are both free, open-source, local-first sandboxes that keep AI coding agents off your bare machine, and both run on Apple silicon (clawk GitHub README and Imbue Sculptor product page, as of 2026-08-08). The choice comes down to the unit of isolation and how many agents you want running.
clawk is the stronger fit when a single agent needs a real machine of its own: a disposable Linux VM with its own kernel, root in the guest, and a DNS-aware outbound allow-list, on macOS 14+ Apple silicon (Apache-2.0). Its Linux support is still experimental and it is pre-1.0, so expect churn. Sculptor is the stronger fit when you want to run several agents at once, each in an isolated git worktree, across Mac or Linux (MIT), provided you already pay for a Claude plan. Neither replaces the other; match the tool to whether you are isolating one powerful agent or parallelizing many.
FAQ
Are clawk and Sculptor free?
Both are free, open-source software as of 2026-08-08: clawk is licensed under Apache-2.0 and Sculptor under MIT. Note that Sculptor's product page states it requires an existing paid Claude plan to use, while clawk can attach Claude Code, Codex, or a plain shell.
Do either of them support Windows?
Neither project's page listed Windows support as of 2026-08-08. clawk requires macOS 14+ on Apple silicon (its Linux provider is experimental), and Sculptor lists Mac Apple silicon and Linux.
What is the main difference between clawk and Sculptor?
clawk gives a single coding agent its own disposable Linux VM per project, with the host filesystem invisible and outbound traffic filtered by an allow-list. Sculptor runs multiple coding agents in parallel, each in an isolated git worktree. One isolates at the machine level; the other parallelizes at the worktree level (both pages, as of 2026-08-08).
Do I need Docker to run clawk?
No. According to the clawk GitHub README as of 2026-08-08, it pulls OCI images and builds bootable disks itself using Apple's Virtualization.framework, so no Docker engine, qemu, or sudo is required. Running a Docker daemon inside a sandbox is a separate, opt-in feature with its own hardware requirements.
Sources
Originally published at https://utilverse.info/compare/clawk-vs-sculptor-two-local-first-sandboxes-for-ai-coding-agents-compared/.
Top comments (0)