Newshot

FlashVMM – jail your AI agent in a MicroVM that boots in 18 ms

Original text(via HN AI)

macOS · Windows · Linuxx86_64 and arm64

Put your agent in jail.

A sandbox for AI runs: every agent task gets its own FlashVM. It's claimed warm in milliseconds, runs whatever the agent wrote behind a real hypervisor boundary, and is thrown away when the task ends. One install, no account, no cloud. We built our own virtual machine for this: FlashVM, leaner and faster than a conventional microVM.

macOS & Linux


        curl -fsSL https://flashvmm.com/install.sh | sudo bash
      

Windows

PowerShell as Administrator. It enables the hypervisor if needed, picks x64 or ARM64 and verifies the checksum.


        irm https://flashvmm.com/install.ps1 | iex
      

Then jail the agent you already use, unchanged: flash agents setup, then cd my-project && claude. It runs in its own VM and sees only that folder. The full tour: flash demo.

What it's for

Let the agent run anything. Keep your machine.

Run code an agent wrote

Scripts, package installs, test suites, and Docker builds run inside a VM with its own kernel. Cap CPU, memory, disk and network only when you want to, and decide what it may reach with --egress. Nothing touches the host.

Give your agent a computer

flash-mcp hands Claude, Cursor or any MCP client the whole lifecycle in 21 tools: create, run commands, copy files, fork, limit what it can reach, call APIs without holding the key, watch, snapshot, restore, tear down.

Start clean, every time

Warm pools keep spares already running, so a task claims one instead of booting. Snapshots restore a prepared environment in milliseconds, and flash fork branches a running VM into copies that carry on from where it was.

Share the GPU

A GPU pool loads an AI model on the host's GPU once and every VM you allow sends it requests. No VM touches the GPU or needs a driver, and snapshots and warm pools keep working. Metal on Apple silicon, Vulkan on Linux and Windows.

How a run works

Claim. Run. Discard.

  • 1ClaimThe task takes a warm spare from the pool, or restores a snapshot. No kernel boot on the hot path.

Claim

The task takes a warm spare from the pool, or restores a snapshot. No kernel boot on the hot path.

  • 2RunThe agent's commands run in the guest with flash exec; exit code, stdout and stderr come back structured. Files go in and out with flash cp; logs, metrics and events stream back live.

Run

The agent's commands run in the guest with flash exec; exit code, stdout and stderr come back structured. Files go in and out with flash cp; logs, metrics and events stream back live.

  • 3DiscardThe VM is removed when the task ends. Nothing it did carries into the next run, unless you snapshot it.

Discard

The VM is removed when the task ends. Nothing it did carries into the next run, unless you snapshot it.


        flash claim spare1 --entry 'npm test'   # a warm spare from the pool
flash logs spare1
flash rm spare1
      

Same CLI, same HTTP API and same MCP tools on every OS. Full walkthrough →

Give it a run.

No accounts, no dashboard. A CLI, a hypervisor, and an MCP server.

The text above was extracted automatically from the source page and may miss images, tables or code blocks. The original is authoritative.

Published by HN AI
This site only summarises and aggregates; copyright stays with the original author. Headlines and summaries follow the source — where they differ, the original wins.
Read the original ↗