DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to run Claude Code on one project inside a sandbox with Brig

Start Claude Code in a microVM that can only see the project folder you name.

Who it is forA developer who wants Claude Code to edit a project, but does not want it to reach the rest of their disk or keychain.

The problemA coding agent running directly on your laptop can read anything your user account can read, including credentials and other repositories.

The outcomeClaude Code runs in its own sandbox against one project folder, and you can stop it or delete the sandbox when you finish.

What you need first

  • A Mac with Apple silicon on macOS 14 or newer, or a Linux host on x86-64 or arm64 (Intel Macs are not supported)
  • Homebrew on macOS, or the Linux install path from brig.sh/docs/install
  • A terminal and a project folder you want the agent to work in
  • An Anthropic account if you want to run Claude Code inside the sandbox

Steps

  1. brew tap brig-sh/brig
  2. brew trust brig-sh/brig
  3. brew install --cask brig
  4. brig doctor
  5. brig run claude ~/code/demo

Prompt for your agent

Using the brig-sh/brig repository, install Brig on this Mac and run `brig doctor` to check the host. Then start a sandbox with `brig run claude <project path>` and report the output of brig doctor and whether the sandbox started. Verify that the project path is the only folder the README says is mounted at /work.

Caveat. The project you name is mounted read-write, so the agent can change or delete any file under it, and Claude Code asks you to log in inside the sandbox.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page