Installation

Via Homebrew (recommended)

brew install bossanova-dev/tap/bossanova

No separate brew tap step is required. The fully qualified formula name points Homebrew at the Bossanova tap during install.

Prerequisites

• A coding-agent CLI matching the agent plugin you intend to use. The bundled claude plugin requires the Claude Code CLI; the bundled codex plugin requires the OpenAI Codex CLI. opencode remains on the roadmap.
• GitHub CLI: required for PR operations.

Manual installation via curl

curl -fsSL https://bossanova.dev/install.sh | sh

The install script downloads the latest GitHub Release binaries for macOS (darwin-amd64, darwin-arm64) and Linux (linux-amd64), configures the bundled plugins, and registers the daemon (launchd on macOS, systemd on Linux). It currently requires the Claude Code CLI, GitHub CLI, and a SHA-256 tool before installing — if you use a different agent plugin, install via Homebrew instead.

Build from source

Requires Homebrew (macOS, or Linuxbrew on Linux) and a Go toolchain. The make deps target installs everything else (go, buf, golangci-lint, jq, gh, gremlins, and the protoc-gen-go / protoc-gen-connect-go buf plugins).

git clone https://github.com/bossanova-dev/bossanova.git
cd bossanova
make deps
make

Binaries land in bin/. The Go-based buf plugins install into $(go env GOPATH)/bin (usually ~/go/bin). If that directory isn't on your PATH, make deps will print the command to add it.

Useful targets

Target	What it does
make build	Build boss and bossd only (skips plugins and cross-compiles)
make plugins	Build the bossd-plugin-* binaries
make test	Run tests across all modules
make lint	Run golangci-lint and buf lint
make clean	Remove bin/ and generated code

Verify your install

Run boss repair doctor. It checks that the daemon can find a working agent plugin and reports any failures it sees.

If the agent runner client wired check fails, confirm that at least one plugin binary (bossd-plugin-claude or bossd-plugin-codex) sits next to bossd or in the Homebrew plugin directory. Then make sure the matching CLI (claude or codex) is on bossd's PATH. Re-run boss repair doctor and confirm all checks pass before launching boss.