Razshy

Wiggle — AI skill for Claude Code

AI community

A working copy of the sandbox that Claude (claude.ai) runs code in.

How to install Wiggle

This entry records only its repository, not the path inside it, so there is no exact command to give. Open Razshy/Wiggle and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Wiggle does

A working copy of the sandbox that Claude (claude.ai) runs code in.

Alternatives in AI

Coding Agent Template — Multi-agent AI coding platform powered by Vercel Sandbox and AI Gateway 1.8k ★
Agenvoy — Self-hosted AI agent harness in a single Go binary — writes, sandbox-tests and repairs its own tools, and lets 474 ★
Mirofish CLI — Multi-agent AI prediction engine - digital sandbox for scenario simulation (fork of 666ghj/MiroFish) 307 ★

README

Wiggle

A working copy of the sandbox that Claude (claude.ai) runs code in.

When Claude executes a command, reads a file, converts a document, or takes a screenshot, it is not running on a web server. It is running inside a small virtual machine, one per conversation. This repository is that machine: the same files, tools, packages, and instructions, packaged so you can run it yourself on Docker, e2b, Modal, or any Linux host.

Codename `wiggle` is what Anthropic calls this VM internally.

Quick start

docker build -t wiggle .
docker run -it wiggle bash

# inside:
soffice --version            # LibreOffice 24.2
python3 -c "import pandas"   # full data science stack
ls /mnt/skills               # the 40 playbooks Claude follows

Want the exact bytes instead of a rebuild? The [GitHub release](https://github.com/Razshy/Wiggle/releases/tag/v1.0-live-rootfs) carries the full filesystem of a live session (8.9 GB, sanitized):

cat wiggle-part-aa wiggle-part-ab > wiggle.tar.zst
zstd -d -c wiggle.tar.zst | docker import - wiggle:live

See [ROOTFS.md](ROOTFS.md) for the full download and verification steps.

How it works

Claude decides to run something and sends the command over a private channel to a supervisor process inside the VM.
The supervisor starts the command with a fixed environment (see meta/env-contract.md) and streams the output back.
The command runs as root with no seccomp and no user sandbox. Inside this VM, root is normal. The isolation that matters is the VM boundary itself.
User files arrive as mounted folders under /mnt/user-data. In production those are remote storage; here they are plain directories.

Machine spec to match if you care about parity: 1 vCPU, 3.9 GiB RAM, no swap. Details in [meta/box-spec.md](meta/box-spec.md).