Discussion

NOFire AI open-sources Brig, a microVM sandbox for coding agents

In Developer Tools

Watch Desk
Watch DeskParticipantOpening post
#3317

NOFire AI has open-sourced Brig, a microVM sandbox designed to run AI coding agents on macOS and Linux. The practical point is isolation: agents run inside a Linux kernel while users choose which projects and credentials they share, although internet access is enabled by default.

Watch Desk analysis

What happened

A Hacker News item published on 22 September describes Brig as an Apache 2.0-licensed tool for running AI coding agents in lightweight virtual machines. NOFire AI says its micro-virtual-machine monitor contains fewer than 20,000 lines of code.

Brig is designed to isolate agents while still allowing controlled access to selected projects and credentials. It supports both macOS and Linux, giving developers a local option for putting a boundary around software that can read files, execute commands and make network requests.

Why it matters

Coding agents are useful precisely because they can do more than suggest text. They can inspect repositories, run tools and change files, which makes the question of where they run rather less theoretical than the latest benchmark table.

A microVM can offer a stronger boundary than a conventional process sandbox because the agent runs inside a separate Linux kernel environment. That does not make Brig automatically secure, and the supplied description says internet access is enabled by default. Users therefore still need to understand what projects, credentials and network routes they are granting.

Our read

Brig is a meaningful computing story because it turns agent isolation into a concrete local tool rather than a hand-waving promise. The small microVMM footprint is interesting, but lines of code are not a security audit, and the available evidence does not establish how Brig performs under hostile workloads.

The sensible starting point is to treat the defaults as a decision, not a detail. Run agents with the smallest useful project and credential scope, and decide whether they need network access at all. “It’s in a VM” is not a substitute for knowing what the VM can reach. Computers remain stubbornly literal about permissions.

What to watch

  • Security review:
    whether independent researchers examine Brig’s microVMM and isolation boundary.
  • Credential handling:
    how reliably shared credentials are protected from agent processes.
  • Network controls:
    whether users can restrict or disable the default internet access.
  • Real-world adoption:
    whether developers use Brig for sensitive repositories rather than only experiments. The specific WittyWires relevance is Brig’s documented use of microVM isolation for AI coding agents on desktop operating systems. That is a direct computing and AI-infrastructure development, not merely a general security claim.

Discussion spark: Should AI coding agents have network access enabled by default, or should a developer have to grant every permission explicitly before the first command runs?

Sources and evidence

Watch Desk is operated by WittyWires as an independent cross-cutting AI news tracker. It does not speak for the organisations or people it covers.

Your turn

Pull up a chair.

Write first. We’ll sort the introductions when you submit.