InstallRoachNet on a Mac

RoachNet Setup puts the app in ~/RoachNet/app and keeps your data in ~/RoachNet/storage. It installs nothing else: no Node, no Docker, no Ollama.

macOS 1.1.4Apple Silicon · macOS 14 or later2 min read
On this page

Before you start

  • An Apple Silicon Mac (M1 or later) running macOS 14 Sonoma or later. Intel Macs aren't supported, and Windows and Linux builds aren't shipped.
  • Room for models. The app itself is small; a model can be under a gigabyte or tens of gigabytes, and you choose which to download.
  • An internet connection for the download and for any models you pull. After that, the local parts of RoachNet work offline.

Download and verify

  1. Download RoachNet-Setup-macOS.dmg and its .sha256 file from the latest release. Keep them in the same folder.

  2. Check the download. The command prints OK when the file matches.

    Terminal
    shasum -a 256 -c RoachNet-Setup-macOS.dmg.sha256
    RoachNet-Setup-macOS.dmg: OK
  3. Open the DMG and run RoachNet Setup.

Open the installer

Not notarized

This build is ad-hoc signed and not Apple-notarized. The first time, macOS says it can't verify RoachNet Setup. Open System Settings › Privacy & Security, scroll down, and choose Open Anyway for RoachNet Setup. It doesn't ask again. The hash check above is what stands in for notarization.

Setup removes the download quarantine from the app it installs, so RoachNet itself opens without the warning.

What Setup does

  1. It checks the Mac first: Apple Silicon, macOS 14 or later, free disk space and a folder it can write to.
  2. It names a starter model sized to your Mac's memory: qwen2.5-coder:1.5b under 16 GB, qwen2.5-coder:7b from 16 GB and qwen2.5-coder:14b from 32 GB.
  3. It stages the new install beside the target folder, starts the staged runtime once as a test, and only then swaps it in. If a step fails, the install rolls back and leaves no staging folders behind.
  4. It may ask once for an administrator password, to add the RoachNet name to /etc/hosts. RoachTail uses that local name, and Setup asks only when the file needs the change.

The first time you open RoachNet, it shows a short introduction and then finishes setting up RoachClaw.

Where things go

Setup installs into ~/RoachNet, in your home folder.

Folder What's in it Back it up?
~/RoachNet/app RoachNet.app, with its helper roachnet-runtime inside. Replaced on every upgrade. No
~/RoachNet/runtime and ~/RoachNet/bin Support files Setup manages. Replaced on every upgrade. No
~/RoachNet/storage Your Vault, models, maps, Org, settings and traces Yes
~/Library/Application Support/roachnet The installer's settings, including the companion token No

Folders and files lists what's inside storage.

Upgrades keep your data

Quit RoachNet and run Setup over the existing install; ~/RoachNet/storage stays as it is. Copy it somewhere first if you might want to roll back: going back to 1.0.7 over 1.1 storage isn't tested. Upgrade, roll back or remove has the steps.

Homebrew instead

The cask downloads the same DMG, checks it against the published hash, and runs the same installer with the companion bridge off. Install with Homebrew has the details.

Terminal
brew tap --force RoachWares/roachnet
brew install --cask roachnet
open ~/RoachNet/app/RoachNet.app

Next steps

That's the install done. Three good places to go from here:

Checked against v1.1.4 · 5 November 2026
esc
↑ ↓ move↵ openesc closeSearches on your device. Nothing is sent anywhere.