One .dmg, no account, nothing phones home. Everything between here and your first running agent is on this page — including the parts other download pages leave out.
VibeCrew is a native Mac app. Everything it keeps lives in ~/.vibecrew/ — a SQLite file, worktrees, pipelines. No cloud, no daemon.
Isolation is git worktrees, not containers: every card’s agent works on its own branch in its own directory, and nothing reaches your main branch without a merge.
claudecodexopencodepiClaude Code, Codex, OpenCode, or Pi — with your own subscription or API key. VibeCrew doesn’t resell model access; your agents run under your accounts.
Alpha builds aren’t signed with an Apple Developer certificate yet, so Gatekeeper flags the first open. It’s a one-time gesture — after that, macOS remembers.
Open the .dmg and drag VibeCrew.app into Applications.
A plain double-click shows the warning without an Open button. Right-click (or Control-click) is the one with the escape hatch.
System Settings ▸ Privacy & Security ▸ scroll down ▸ Open Anyway.
The first-run sheet registers a git repo by its path, creates a project on top of it, and picks your default coding agent. Want a do-over later? Settings ▸ Data ▸ Reset onboarding.
Settings ▸ Agents ▸ Plugins ▸ Manage… ▸ Sync Catalog installs VibeCrew’s skills and subagents into each CLI’s own global config. It never overwrites a file it didn’t write.
Settings ▸ Assistant ▸ Handbook ▸ Download handbook — so the agent inside the app can answer questions about the app. Optional, worth it.
Give it a pipeline, press Start, and watch it in Fleet — or don’t. That’s rather the point.
You’ll open Agents and Pipelines in week one; the rest can wait until they’re needed.
Want to see what you’re getting before the .dmg finishes?
Take the tour