Who it is forA developer who wants to run an unfamiliar script, package or tool before trusting it on their own machine.
The problemRunning untested code directly on your laptop gives it the same access you have to your files, keychain and SSH agent.
The outcomeThe code runs in a sandbox with its own kernel and home directory, and deleting the sandbox removes its guest home.
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
brig doctormkdir -p ~/code/demobrig run ubuntu ~/code/demobrig stop ubuntu(inferred, check the README)brig rm ubuntu(inferred, check the README)
Prompt for your agent
Using the brig-sh/brig repository, run `brig run ubuntu <project path>` to open a root shell in a sandbox, then run the test command the user gives you inside it. Report the output and then run `brig rm ubuntu`. Verify that the README says `brig rm` removes the sandbox and deletes its guest home.
Caveat. The project folder is still mounted read-write at /work, so code run in the sandbox can change files under that folder.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: 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