Brewboard is a small Next.js app for tracking craft beers — it ships with six features already written and waiting in the backlog. Use it to get a feel for the full Aigon workflow before adding Aigon to a real project.

You can drive Aigon from three different surfaces. This tutorial walks through all three:

1. The dashboard — click-to-run from the browser UI
2. Slash commands — inside a Claude Code session
3. The CLI — from your terminal

Each section covers Drive mode, Fleet mode, and Autonomous mode.

What’s in the repo

Brewboard has six pre-written feature specs, each describing a small, self-contained change:

Each spec has acceptance criteria, a technical approach, and out-of-scope constraints — so the agent has clear boundaries and knows exactly when it’s done.

Set up Brewboard

git clone https://github.com/jayvee/brewboard-seed.git ~/src/brewboard
cd ~/src/brewboard
git remote remove origin        # prevent accidental pushes — this is a local sandbox
npm install

aigon init
aigon install-agent cc          # swap for gg, cx, or cu if you prefer

aigon server start --persistent        # install as a persistent system service
aigon server add ~/src/brewboard       # register the repo with the dashboard

1. From the dashboard

The dashboard is the most visual way to interact with Aigon. Open http://localhost:4100  and navigate to the Brewboard repo.

Drive mode

In the Pipeline view, find feature 01 — Dark Mode in the Backlog column. Click Start on the card — a picker appears where you select one agent to drive the implementation.

Click Start. Aigon creates a worktree, opens a tmux session, and begins implementation.

Watch the card update in real-time:

• Status moves from Starting → Working → Submitted
• The Sessions panel shows agent liveness with heartbeat updates every 30s
• Elapsed time and cost appear on the card as the session runs

Before closing, click the globe icon on the card to open a preview of that worktree’s dev server in your browser — eyeball the changes before committing to them. When you’re happy, click Accept & Close. Aigon merges the branch to main, moves the spec to Done, and cleans up the worktree.

Fleet mode

Fleet mode runs two agents on the same feature simultaneously. Find feature 04 — Rating System in the Backlog. Click Start and select two agents (e.g. Claude Code + Gemini CLI).

Two cards appear for the same feature — one per agent — both updating independently. When both show Submitted, click Evaluate to open a review session that compares both implementations and recommends a winner. Then click Accept & Close on your preferred card to merge it.

Autonomous mode

For a completely hands-off run, find feature 02 — Brewery Import, open its action menu, and click Start Autonomously.

A modal appears where you select an implementation agent, a reviewer, and when to stop. The default stop point is after close — the full lifecycle runs unattended.

Click Start Autonomously. The AutoConductor spawns the implementation session, waits for it to finish, automatically runs a review, and calls feature-close — all without any further input from you.

Check the Reports tab after the session completes to see token usage and cost.

2. From slash commands in Claude

Open a Claude Code session in the Brewboard directory (or any worktree), and use /aigon: slash commands directly in the conversation.

Drive mode

/aigon:feature-start 01 cc

Claude creates the worktree and begins implementing feature 01. You can watch it work, give feedback mid-implementation, or let it run to completion. When it signals done:

/aigon:feature-close 01

Fleet mode

Start two agents on feature 04 from inside Claude:

/aigon:feature-start 04 cc gg

Both agents start in parallel. Once both signal submitted, run the evaluation:

/aigon:feature-eval 04

The eval agent reads both diffs and writes a recommendation. Close with your chosen agent:

/aigon:feature-close 04 cc

Autonomous mode

Hand the whole lifecycle over to the AutoConductor:

/aigon:feature-autonomous-start 02 --agent cc --review-agent gg

The conductor handles implementation → review → close automatically. You’ll see the feature move through the pipeline in the dashboard without any further commands.

3. From the CLI

All Aigon operations are available as CLI commands — useful for scripting, CI, or when you prefer the terminal.

Drive mode

aigon feature-start 01 cc

This creates an isolated worktree at ~/src/brewboard-worktrees/feature-01-cc-dark-mode/, launches Claude Code in a tmux session, and runs feature-do automatically inside it. Attach to watch:

tmux attach -t brewboard-f1-cc-dark-mode

When the agent signals submitted, close from the terminal:

aigon feature-close 01

Fleet mode

aigon feature-start 04 cc gg    # requires both Claude Code and Gemini CLI

Two worktrees are created and both agents start implementing independently. When both are done, evaluate and close:

aigon feature-eval 04           # opens a review session comparing both diffs
aigon feature-close 04 cc       # merge cc's branch; or swap for gg

Autonomous mode

aigon feature-autonomous-start 02 --agent cc --review-agent gg

Walk away — the AutoConductor handles implementation, review, and merge. Check aigon board when you’re back to see the result:

aigon board

Reset and repeat

The seed repo is designed to be reset between runs:

aigon seed-reset ~/src/brewboard

This wipes all worktrees, branches, workflow state, and git history and re-clones from the seed — so you can try a different surface, mode, or agent from scratch.

Next steps

• Drive Mode — full lifecycle reference for single-agent work
• Fleet Mode — how parallel agents and evaluation work
• Autonomous Mode — hands-off loops with the AutoConductor
• Dashboard — what each panel shows and how to use it