deankerr

Orbstack Sandbox — AI skill for Claude Code

AI community

Sandboxed OrbStack VMs for LLM coding agents — locks down host filesystem access so agents in permissive modes can't damage the host.

How to install Orbstack Sandbox

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

What Orbstack Sandbox does

Sandboxed OrbStack VMs for LLM coding agents — locks down host filesystem access so agents in permissive modes can't damage the host.

Alternatives in AI

  • Oh My Claudecode — 32 specialized agents and 7 execution modes for Claude Code, with smart model routing and automatic paralleliz 10.9k ★
  • Coding Agent Template — Multi-agent AI coding platform powered by Vercel Sandbox and AI Gateway 1.8k ★
  • Rb Setup — First-time setup 1.3k ★

README

orbstack-sandbox

Sandboxed OrbStack VMs for LLM coding agents. OrbStack is a fast, lightweight way to run Linux VMs on macOS — but it mounts the host filesystem with full access by default. This locks that down so agents running in permissive modes (e.g. `claude --dangerously-skip-permissions`) can work on dev tasks without risking the host machine.

It's a seatbelt, not a jail — it guards against accidental host damage and credential access, not a determined attacker. Don't rely on it to contain untrusted or adversarial code.

Quick Start

# Set up a new VM (or configure existing one)
./setup.sh myvm

# Create a sandboxed user
./create-user.sh myvm agent

# Connect as sandboxed user
orb -m myvm -u agent

How It Works

OrbStack mounts `/Users` and `/mnt/mac` into every VM with full read/write access — exposing your home directory, SSH keys, and credentials to any process in the VM.

This repo gives each sandbox user a custom login shell that runs `unshare --mount` to build a private mount namespace, overlays the macOS paths with empty tmpfs mounts, then uses `setpriv` to drop to the unprivileged user — so there is no sudo inside the sandbox. Each sandbox user sees empty directories in place of macOS paths:

Admin user:              Sandboxed user:
/Users → macOS home      /Users → empty
/mnt/mac → macOS root    /mnt/mac → empty

The admin user retains full access and can read/write sandbox home directories via POSIX ACLs (no sudo needed).

Scripts

Script Purpose
setup.sh [machine] Create/configure Ubuntu VM with zsh, homebrew, starship, dev tools
create-user.sh Create sandboxed user with isolated mount namespace

setup.sh

  • Creates Ubuntu VM (if needed)
  • Installs system pa