macOS Apple Silicon
brew install --cask ephor/tap/warpforgeThe cask installs the same signed, notarized build as the DMG. Homebrew handles the initial install; the built-in updater takes over from there (the cask declares auto_updates, so brew upgrade never fights it).
- Open the latest Warpforge release.
- Download
Warpforge_<version>_aarch64.dmg. - Open the DMG and drag Warpforge into Applications.
- Launch it and select the coding agents you want enabled.
The build is signed with a Developer ID certificate and notarized by Apple, so it opens without Gatekeeper workarounds. It needs macOS 11 or newer on an Apple Silicon Mac and ships its own daemon — no Rust toolchain or source checkout required.
Updates are built in and signed. When a new version is available a button appears in the top bar naming it — one click downloads, a second restarts to finish, and progress or failure stays on that same button rather than stalling out of sight. Nothing installs in the background. An update carries both the desktop UI and its matching daemon, verifies an exact version and protocol handshake, and is refused with a clear list of blockers while agent tasks or runtime transitions are still active rather than interrupting work.
Requirements beyond the app itself
The signed app needs no Rust toolchain or source checkout, but two features shell out to CLIs it does not bundle — install them separately if you want those features:
- Node.js and
npmonPATH. Powers the one-click install/update for most agents (see the agent table) and for editor language servers. Without it, you can still point Warpforge at an agent binary you installed yourself. - GitHub CLI (
gh), authenticated. Needed for Open pull request (gh pr createinsrc/daemon/diff.rs) and fetching attachments on private issues (src/daemon/attachment.rs). Backlog GitHub sync prefers a PAT (repo+read:projectin Settings → Trackers) and falls back togh(deprecated for backlog only — slow per-request process, will be removed for backlog;ghitself remains required for opening PRs, there is no PR list view in the app).
Reuse your existing agent login
Warpforge adds no model account or API-key layer. It looks for supported agent binaries on your PATH, speaks the Agent Client Protocol (ACP) to them over stdio, and stores your enabled-agent selection locally. If Claude Code, Codex, or OpenCode is already installed and authenticated, that setup is reused as-is — the CLI keeps owning authentication, model access, and the coding itself.
See Bring your own agents for the full list of supported agents and how to add a custom one.
Next steps
- Why Warpforge? — the coordination problem it solves.
- Choosing your mode — single agent, orchestrator, or a review pipeline.
- Projects and their runtime — register a project and bring services online.
- Cross-harness memory — one memory your agents share.
- Building from source — only needed to develop Warpforge itself.