The127

Aibox — AI skill for Claude Code

AI community

AI in a box. Run Claude in a secure microvm environment.

How to install Aibox

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

What Aibox does

AI in a box. Run Claude in a secure microvm environment.

Alternatives in AI

Cindy — Consider it done 2.3k ★
Phantom — An AI co-worker with its own computer 1.3k ★
Cwc Long Running Agents — Claude Code's built-in /goal command gives you a generator/evaluator loop out of the box: set a completion con 668 ★

README

aibox

[![ci](https://github.com/The127/aibox/actions/workflows/ci.yml/badge.svg?branch=main)](https://github.com/The127/aibox/actions/workflows/ci.yml)

aibox runs [Claude Code](https://code.claude.com) in a small virtual machine on your computer.

![aibox run starts Claude Code in a VM](docs/demo.gif)

Claude Code can read and change files, run commands and access the internet. That is what makes it useful, but it also means a bad prompt or a malicious file in a repository can make it do things you did not want. aibox limits the damage. Claude Code only sees the files you give it, and it can only connect to hosts you allow.

You can use aibox in two ways:

aibox run starts Claude Code in your project folder, like you would on your machine. Changes show up in the folder right away.
aibox task hands Claude Code a job to do on its own. It works on a clone of the last commit and you get its commits back to review. The VM is deleted afterwards.

aibox runs on Linux with QEMU and on macOS with Virtualization.framework. The VM boots in about a second.

Note that with `aibox run` the VM can change anything in your project folder, `.git` included. Treat those changes like a pull request from a stranger. Read [What the VM writes](https://the127.github.io/aibox/what-the-vm-writes.html) before you start.

Why a VM

Claude Code's own sandbox only covers shell commands. Its file tools, MCP servers and hooks still run on your machine. A Docker container covers the whole process, but shares your kernel. A VM has its own kernel, so a kernel bug alone is not enough to get out. aibox keeps that VM small, with no network card and a proxy as its only way to the network. [Why a VM](https://the127.github.io/aibox/introduction.html#why-a-vm) compares aibox with these, Apple's container tool and Docker Sandboxes.