reactive.org enterprises omarchy-vm

A SANDBOX FOR AI-NATIVE DEVELOPMENT

Omarchy VM Manager icon

Use Omarchy, not just try it.

A native macOS manager for running many Omarchy virtual machines side by side. It's a high-fidelity, focused security sandbox for AI-based development, built heavily on the work of the Try Omarchy team.

macOS 15+ Apple silicon Try Omarchy v1.3.0 SwiftUI + CLI MIT
View on GitHub Pair with dev-vm
A new guest starting beside the others: the kit is verified, the disk prepared, and it's running.

WHY

A real desktop for your agents, fenced off from your Mac.

TAKE THE TOUR

One window for every guest.

A native sidebar lists your guests, and each one has its own Home, Virtual Machine, Network, Startup, SSH and Spaces pages. These are real captures of version 0.9.3.

A 48-second captioned walk through twelve screens of the app.
The manager library: two stopped guests with their cores, memory and disk, and Import Factory and New VM controls.
Your virtual machines. Every guest, its state and resources at a glance.
Guest Home for Dev Code: ready to launch, independent disk and NAT network, with an experimental suspend panel and quick settings.
Guest Home. Launch readiness for each guest, plus quick settings.
The Virtual Machine page: 8 processor cores, 20 GiB memory, a 64 GiB disk and the recorded factory image.
Resources and factory. CPU, memory, disk and the image it was built from.
The Network page: NAT networking, a localhost SSH port forward to guest port 22, and host sharing turned off.
Networking. NAT, one localhost SSH forward, and host sharing off.
The Spaces page with steps to assign a running guest to a Mission Control desktop from its Dock icon.
Mission Control Spaces. Give each guest a desktop of its own.
The Runtime page: the pinned Try Omarchy kit with host preflight passed, and a known graphics startup issue.
Runtime. Host checks, the pinned kit, and known issues stated plainly.

BRING YOUR OWN IMAGE

Start from the image you want.

Every guest picks its factory image when it's created: the official one, or a custom image you've prepared.

The Import Factory sheet: choose a prepared factory bundle folder containing factory.json and reviewed-factory.json; the app checks the image, provisioning files and compatibility.
Import Factory. Choose a prepared bundle; the app verifies it first.
The New VM form: name, factory image picker with an Import Factory button, memory, cores, disk capacity, clipboard, immersive mode, owner setup and SSH.
New VM. Pick the factory image per guest.

BETTER TOGETHER

Make every guest yours with dev-vm.

Pair it with dev-vm for a declarative, fully configured developer environment. dev-vm can build a lean coding image and import it for you, asks the manager to create and start a named guest, then adds your tools, theme and layout and checks the result, so every guest comes up just the way you like it.

A running guest, Dev Omarchy, in the manager: independent disk, shared NAT network, 8 cores and 20 GiB of memory, with a focus-aware clipboard.
A running guest: independent disk, NAT network, focus-aware clipboard.

THE CLI

Guests on demand, from Claude or the terminal.

The omarchy-vm CLI drives the same manager as the app, opening it in the background when needed, and replies in concise JSON that Claude Code reads easily. Open Claude in your checkout and ask, or add the repository's bin folder to your PATH and run the commands yourself.

  1. Create a guest from the official image and wait until you can SSH in.

    Create a guest called "dev" from the official image with 4 CPUs, 4 GiB of memory and a 64 GiB disk. Tell me when SSH is ready.
    omarchy-vm create dev --factory official \--memory 4GiB --cpus 4 --disk 64GiB \--start --wait ssh --timeout 1800

  2. Connect with the managed key and pinned host identity.

    Give me the command to SSH into "dev".
    eval "$(omarchy-vm get dev | jq -r .guest.ssh.command)"

  3. See what you have running.

    Which of my guests are running?
    omarchy-vm list

  4. Set a guest aside without shutting it down, then pick up where you left off.

    Pause "dev" until I need it again.
    omarchy-vm pause devomarchy-vm resume dev

  5. Give a guest more room. Changes need it stopped, and disks only grow.

    Give "dev" 6 CPUs, 5 GiB of memory and a 128 GiB disk.
    omarchy-vm stop dev --waitomarchy-vm update dev --memory 5GiB --cpus 6 --disk 128GiBomarchy-vm start dev --wait ssh

  6. Import a custom image, then create guests from it by its manifest SHA-256.

    Import the factory at ~/Prepared.factory and create "custom-dev" from it.
    omarchy-vm factory-import /absolute/path/Prepared.factoryomarchy-vm factoriesomarchy-vm create custom-dev --factory MANIFEST_SHA256 \--memory 4GiB --cpus 4 --disk 64GiBomarchy-vm start custom-dev --wait ssh

  7. Finished with a guest? It goes to the macOS Trash, not oblivion.

    Stop "dev" and move it to the Trash.
    omarchy-vm stop dev --waitomarchy-vm delete dev

Every command and flag is in the CLI reference.

GET STARTED

Build it on your Mac.

On Apple silicon with macOS 15+, Swift 6 and Python 3.10+. Docker is needed for the guest package build.

  1. Get the project and its pinned Try Omarchy kit.

    git clone https://github.com/reactive-org/omarchy-vm-manager.gitcd omarchy-vm-managergit submodule update --init

  2. Fetch and verify the kit, then build, test and check the app.

    make fetch-kit patched-kit testmake app verify-app

  3. Open it, choose New VM, and launch.

    make run

Pre-release. Omarchy VM Manager is currently a private debug build: build it from source, and expect the rough edges noted in the repository. A signed, notarized release is the intended way to ship it. The illustrated user guide walks through the app and CLI.

Built on Try Omarchy. Omarchy is a pending trademark of the Omacom Foundation.