Aigon

Aigon is a spec-driven multi-agent harness — orchestrate Claude Code, Gemini CLI, and Codex CLI from one Kanban board, one CLI, or one slash command.
One Kanban for many agents — on real branches, in real worktrees, against real specs.

▶ Watch the 3-minute intro on YouTube

Beta: Aigon is early-access software. APIs and config formats may change between releases. Use it, file issues, and expect rough edges. Stable release coming soon.

Aigon is an open source project by Sen Labs. Follow aigon.build for updates.

---

What is Aigon?

Aigon is a spec-driven harness for orchestrating multiple AI coding agents on the same codebase. Each feature is a Markdown spec in git; each agent runs in its own git worktree under tmux; the lifecycle moves through inbox → backlog → in-progress → review → done on a local Kanban board. Aigon doesn't try to be a model — it orchestrates a growing list of agent CLIs as engines.

You work with Aigon from wherever you already are: a web dashboard on localhost, slash commands inside your agent (Claude Code, Gemini CLI, Codex CLI, Cursor, OpenCode, Kimi, Amp), or direct CLI commands in your terminal. All three surfaces read and write the same Markdown specs in your repo — no SaaS account, no vendor lock-in, no proprietary state.

It works with the AI coding tools you already use:

• 🤖 Claude Code (cc)
• 💎 Gemini CLI (gg)
• 📟 Codex CLI (cx)
• 🎯 Cursor (cu)
• 🧭 OpenCode (op)
• 🌙 Kimi Code CLI (km)
• ⚡ Amp (am)

Mix and match. Aigon doesn't care which model writes the code — it just manages the workflow around them.

Why Aigon?

• Bring your own subscriptions — use the AI products you already pay for (Claude, Codex, Gemini, Cursor, OpenCode, Kimi, Amp); no separate Aigon billing, no token packs, no markup.
• Stay in the flow when a subscription lapses — switch agents or accounts mid-session instead of being stuck on one vendor's meter.
• Spec-driven development you control — features and research live as Markdown specs that can be built, shipped, reset, and rebuilt for clean handoffs and retries.
• Autonomous and multi-agent workflows — configure who drafts, implements, and reviews, then run long loops through a pre-built push/merge lifecycle.
• Context that compounds — specs and implementation summaries feed forward into later work, so context accrues in the repo rather than evaporating with a session.
• Transparent, local, team-aligned — agents run in plain tmux sessions you can attach to; CLI + git on your machine, no required hosted platform, and fits GitHub PR review cleanly.

Quick start

Prerequisites: Node.js 18+, Git 2.20+, and tmux (for Fleet/worktree mode). See the Getting Started guide for platform-specific install instructions.

# Install aigon globally (beta)
npm install -g @senlabsai/aigon@next

# First-time setup — installs agent CLIs, configures terminal,
# starts the dashboard. Auto-launches on first aigon command, or
# run it explicitly:
aigon setup

# Bring aigon into your project
cd /path/to/your/project
aigon apply                            # Bootstraps .aigon/, kanban folders, hooks
aigon install-agent cc                 # Install the Claude Code agent (others: gg, cx, cu, op, km, am)
aigon doctor                           # Verify environment

Aigon gives you three surfaces over the same Markdown specs in your repo. Pick the one that fits the moment — the state is identical across all three.

1. Dashboard — the recommended starting point

The dashboard is the daily command center. It's always-on after aigon setup and gives you the Kanban view of every feature, research topic, and piece of feedback across its lifecycle:

aigon server start                     # Starts at http://localhost:4100

Open the dashboard, click "New Feature", write a one-line description, and drag the card from inbox → backlog → in-progress. Click an agent button (cc, cx, cu, …) and a worktree spins up with a live tmux session you can attach to. Watch progress in the Monitor tab, review the diff in the in-evaluation column, and merge with one click. No commands to memorise.

The Reports tab shows cycle time, commits per feature, and rework ratio across your whole pipeline. Telemetry breaks down token spend per agent and activity. Open it on your phone over LAN or Tailscale to check in from the couch.

2. Slash commands — when you're already inside an agent

If you're already in Claude Code, Gemini CLI, Codex, Cursor, OpenCode, Kimi, or Amp, drive Aigon from where you are. The fastest path is /aigon:feature-now:

/aigon:feature-now dark-mode
Add a dark mode toggle with system preference detection, persist
the choice in localStorage, and default to the system preference.

That one command creates the spec, assigns an ID, creates a feature branch, and starts implementing — all in your current repo, using your default agent. You stay in the agent the whole time.

3. CLI — terminal-native flow

For terminal-first workflows or scripting, drive Aigon by command. feature-create writes a bare spec from your description and launches Claude Code (cc) interactively with the drafting context pre-loaded:

aigon feature-create dark-mode --agent cc "dark mode toggle with system preference detection, persisted in localStorage"

You have a real conversation with the agent — it asks clarifying questions, proposes user stories and acceptance criteria, you push back and iterate, and when you're satisfied you exit the session. The drafted spec lands in docs/specs/features/01-inbox/ for a final review. When you're happy with the draft, move it forward:

aigon feature-prioritise dark-mode           # Assigns an ID, moves to backlog
aigon feature-start dark-mode cc             # Single-agent Drive mode in a worktree
# or
aigon feature-start dark-mode cc cx          # Fleet mode — Claude and Codex race the implementation
aigon feature-eval dark-mode                 # Compare results, pick the winner

Demo

▶ Introducing Aigon — Spec-Driven Development with Parallel Agents & AFK Mode (3 min)

The Aigon dashboard shows features across their full lifecycle — inbox → backlog → in-progress → in-evaluation → done — with live agent session status, commit activity, telemetry, and the repo-wide All Items index for features, research, and feedback.

Documentation

Full documentation lives at aigon.build/docs:

• 📘 Getting Started — install and run your first feature
• 🧭 Core Concepts — workflows, execution modes, reliability
• 🛠 Guides — Drive, Fleet, Autopilot, Research, Dashboard, Telemetry
• 📚 CLI Reference — every command documented
• 🔍 Agents — Claude, Gemini, Codex, Cursor, OpenCode, Kimi, Amp setup

Aigon Pro

Aigon Pro is a commercial tier that extends the free workflow with three things the open-source side intentionally doesn't do:

• Autonomous orchestration — AutoConductor runs implement → review → close unattended, so you can hand off a feature and come back to a merged PR
• Insights — deeper analytics over your whole feature history: agent quality trends, cost per delivered change, token efficiency over time, agent-vs-agent comparisons
• AI-powered coaching — recommendations based on your workflow patterns, so the system learns what "shipping well" looks like for your team

Aigon Pro is in private beta — invitation only. Email john@aigon.build with your GitHub username to request access. Once you have a key, the installation guide walks through setup; the Pro page has the full feature overview.

The free tier — Drive mode, manual Fleet, the dashboard, interactive evaluation/review, telemetry, and basic reports — is complete and stays free and open source.

Community and support

• 💬 GitHub Discussions — questions, workflows, design ideas
• 🐛 Issues — bugs and concrete feature requests
• 📖 Docs — the full manual
• 🧑‍💻 Contributing — how to set up a dev environment and submit PRs
• 🔒 Security policy — how to report vulnerabilities privately
• 📰 aigon.build — follow here for launch updates, release notes, and Pro announcements
• 🏢 Sen Labs — the company behind Aigon

License

Apache License 2.0 — Copyright 2025–2026 Sen Labs