SkillFoxx

ArcBox CLI

ArcBox runs Claude Code in a disposable microVM on a Mac: its own kernel, an empty workspace and a start in about a second

  • 4,302 ★ on the repository
  • Last commit
  • Apache-2.0
CLI

Extended access

Why this level

  • Switches off the agent's permission prompts inside the sandbox
  • The agent needs the API key inside the sandbox and runs commands without prompts
All reasons and checks

arcboxlabs/arcboxAuthor:arcboxlabs

Install

Works in

Manual install

brew install --cask arcboxlabs/tap/arcbox

The first README command. Then `abctl daemon start`.

Access and checks

How we review

Extended accessThe tool runs code or makes network calls and only reads external data.

  • Switches off the agent's permission prompts inside the sandbox
  • The agent needs the API key inside the sandbox and runs commands without prompts

This is third-party code. Review the repository files before installing.

What it does

ArcBox is an open-source container and VM runtime for macOS written in Rust: a Docker-compatible engine, Kubernetes and full Linux and macOS machines. For agents it offers disposable microVMs with their own kernel, filesystem and network. The `abctl claude` command builds a sandbox from a built-in template and attaches the terminal to Claude Code inside it. The agent's permission prompts are switched off: the VM is the boundary. Nothing from the host is mounted, `/workspace` starts empty, the agent clones what it needs and results are copied back. The `abctl sandbox` commands create sandboxes from an image or Dockerfile, copy files, expose ports and snapshot for fast starts.

Who it is for. Mac owners on Apple Silicon M3 or newer who want to run an agent in no-prompt mode without risking the main system.

Good fit when

  • An agent is to run without prompts but on a separate machine.
  • An unknown script or binary is run to see what it does.
  • Two independent agent sessions run in parallel without interfering.
  • An app image is checked in a sandbox with memory and time limits.
  • A clean state is saved as a snapshot and every start becomes instant.

Not a fit when

  • A Mac on Intel or Apple Silicon older than M3, or macOS older than 15: sandboxes will not start.
  • The agent needs direct access to your project on the host: nothing is mounted.
  • You only need Docker for containers and Docker Desktop suits you.

Example request

Start Claude Code in an ArcBox sandbox, let it clone the repository, run the tests and write a report to a file I will copy out afterwards.

Limitations

Sandboxes need nested virtualization: Apple Silicon M3 or newer and macOS 15 or newer on the default VZ backend, and on other hosts the commands fail fast with an error. The project is in public beta. `abctl claude` switches off the agent prompts, so protection rests on VM isolation alone. The `ANTHROPIC_API_KEY` is set through an environment variable and the agent needs it to work, so use a key with a spending limit.

How to disable. Stop the service with `abctl daemon stop` and remove sandboxes through `abctl sandbox`. Uninstall the app via Homebrew, the config lives in `~/.config/arcbox/config.toml`.

FAQ

How do I install it?

Run `brew install --cask arcboxlabs/tap/arcbox` or the install script from the README, then `abctl daemon start`. `abctl doctor` checks the state.

What hardware do sandboxes need?

Apple Silicon M3 or newer and macOS 15 or newer. On other hosts `sandbox` commands fail immediately with an error.

What is inside `abctl claude`?

A sandbox from a built-in template and Claude Code inside it. The first run builds the image, later runs start in about a second.

How do I get results out?

With `abctl sandbox cp <id>:/tmp/out.tgz .`. Nothing from the host is mounted, so files are copied explicitly.

Can I start a second session?

Yes, `abctl claude --id review` creates an independent session. Arguments after `--` go to the agent, for example `-- --model opus`.

Discussion

No questions or reviews yet.

CLI tools

AgentBox runs Claude Code, Codex and Open Code in separate virtual machines on your PC, a self-hosted server or a cloud.

CLIExtended access580

ClaudeBox runs Claude Code in Docker with language profiles, session slots and a firewall with an allowlist of addresses.

CLIExtended access1.2K

Runs each agent stage in its own micro-VM: Claude, Codex, Ollama or any CLI, with OTLP tracing

CLIExtended access89

ExitBox runs Claude, Codex, Cursor and other agents in rootless containers: a domain allowlist and secrets in an encrypted vault.

CLIExtended access107

Brig runs Claude Code and other coding agents inside an isolated microVM on your machine with access to one project only.

CLIExtended access266

A CLI that runs Claude Code and Codex in isolated Docker containers with a firewall, worktrees and a no-Dockerfile image.

CLIExtended access59

README in short

One daemon and one CLI serve four workload kinds: containers, agent sandboxes, Linux machines and macOS guests. Everything runs locally with no cloud control plane.

README badge

Report a problem