Skip to content

Build from source

Prerequisites and commands to run Warpforge from a source checkout.

Updated View as Markdown

Only needed to develop Warpforge itself or to run it where no build is published. Install is the recommended path for everyday use.

Prerequisites

  • Rust and Cargo
  • Bun 1.3 or newer
  • Git
  • Tauri 2 system prerequisites
  • Node.js and npm on PATH — the daemon shells out to npm to install/update most agents and language servers
  • At least one supported coding-agent CLI, installed and authenticated
  • GitHub CLI (gh), authenticated — needed for Open pull request and for the GitHub backlog
  • Optional: Docker Compose, kubectl — only needed if a project’s workspace.yaml uses them
  • Optional: Python 3 — only needed for cargo test (one daemon shutdown test spawns a Python listener to simulate a foreign process)

Run the desktop app

git clone https://github.com/warpforgehq/warpforge.git
cd warpforge/desktop
bun install
bun run tauri dev

The Tauri shell builds and starts the matching Rust daemon as a sidecar. bun install also wires up the pre-commit hook that runs the fast CI checks against staged files.

Run the checks

cargo test --locked

cd desktop
bun run test
bun run typecheck
bun run lint

Build a local desktop bundle

cd desktop
bun run tauri build

Official releases additionally use protected updater signing keys, Developer ID signing, Apple notarization, immutable release tags, and draft-asset verification in GitHub Actions — see RELEASING.md in the repository.

Navigation

Type to search…

↑↓ navigate↵ selectEsc close