Docs

Quickstart

A single Go binary, no runtime dependencies. Install it, start the daemon, and open the dashboard. Here’s the path from zero to a running team.

1 · Install

Get the binary.

Install from the Homebrew tap on macOS, or build from source with Go. Cross-platform binaries ship via the GitHub releases.

Homebrew tap Releases

install

 # macOS — Homebrew tap
brew install agenity-org/agenity/agenity
# from source (any platform with Go)
go install github.com/agenity-org/agenity@latest

2 · Run

Start the daemon.

Detect your sessions, start the daemon, and open the interactive dashboard. The daemon runs as a user-level service.

run

agenity init # detect sessions + write config
agenity start # start the daemon
agenity # open the dashboard
agenity status # one-shot status of all sessions

3 · First team

Spawn a team.

From the dashboard, spawn agents into a team and give each a role. Agents get a role-aware briefing, the MCP toolkit, and a shared team canon — then start talking to each other over the knock pattern.

Mix flavors freely: a Claude Code lead with free-tier Gemini, Qwen, Copilot, or opencode workers that cross-check each other.

dashboard · spawn

 # in the dashboard spawn wizard
team: build-squad
agents:
  - architect flavor=claude-code
- worker flavor=opencode+groq
- qa flavor=gemini-cli # they discover each other: list_sessions() # → architect, worker, qa

Architecture

How it fits together.

A central daemon per org, a runner per agent, and a browser dashboard — all speaking A2A and MCP. The full design lives in the repo.

Daemon

Per-org central service — session registry, auth, operator API, dashboard backend, federation client.

Runner

PID 1 of each agent pod — hosts the A2A endpoint and the agent’s MCP server, owns the PTY.

Dashboard

Browser control room — Talk + Terminal per agent, the shared ledger, operator commands.

A2A + MCP

One A2A path for inter-agent traffic; MCP (Streamable-HTTP) for each agent’s tool calls.

README & docs on GitHub Issue tracker