Installation
Clone the repository and link the CLI globally:
git clone https://github.com/jayvee/aigon.git
cd aigon
npm install
npm linkVerify the install:
aigon --versionOptional tools
Aigon works without these, but they unlock additional capabilities:
| Tool | What it enables | Install |
|---|---|---|
| tmux | Persistent agent sessions that survive terminal closes | brew install tmux |
| gitleaks | Secret scanning in pre-commit hooks and merge gates | brew install gitleaks |
| Playwright | Dashboard end-to-end tests | npx playwright install |
Agent CLIs
Install at least one agent CLI to use aigon:
| Agent | CLI | Install |
|---|---|---|
| Claude Code | claude | brew install claude |
| Gemini CLI | gemini | npm install -g @anthropic-ai/gemini-cli |
| Codex CLI | codex | npm install -g @openai/codex |
| Cursor | cursor | cursor.com |
You don’t need all of them — install whichever you have access to. Fleet mode works best with 2+ agents.
Initialize a project
Navigate to any Git repository and run:
cd /path/to/your/project
aigon initThis creates the docs/specs/ folder structure with Kanban lanes for features, research, and feedback.
Then install the agents you want to use:
aigon install-agent cc gg # Claude Code + Gemini CLI| Code | Agent | Slash prefix |
|---|---|---|
cc | Claude Code | /aigon: |
gg | Gemini CLI | /aigon: |
cx | Codex CLI | /prompts:aigon- |
cu | Cursor | /aigon- |
Install only the agents you have access to. You can add more later with aigon install-agent.
Three ways to interact
| Slash Commands | CLI | Dashboard | |
|---|---|---|---|
| Where | Inside an agent session | Terminal / shell | Browser UI |
| Best for | Writing specs, implementing features | Orchestration, setup, scripting | Visual overview, monitoring Fleet runs |
| Example | /aigon:feature-do 07 | aigon feature-start 07 cc gg | Click “Start feature” on a kanban card |
All three surfaces drive the same underlying workflow. Mix them freely.
Your first feature
The fastest path from idea to implementation is feature-now. Describe what you want — the agent creates a spec, assigns an ID, sets up the workspace, and starts implementing:
/aigon:feature-now dark-mode
Add a dark mode toggle to the top-right of the site header.
Use CSS custom properties for theming. Default to system preference.
Store the user's choice in localStorage.This is a normal agent conversation — you can go back and forth, refine requirements, ask questions, and iterate on the spec before the agent starts coding. The difference is that the conversation is anchored to a feature spec with acceptance criteria, so decisions are captured rather than lost in chat history.
Step by step (the full loop)
For more control, use the individual commands:
# 1. Create a feature — describe what you want
/aigon:feature-create dark-mode
Add a dark/light mode toggle with system preference detection...
# 2. Prioritise — assigns an ID, moves to backlog
/aigon:feature-prioritise dark-mode
# → Assigned ID: 07
# 3. Start — creates workspace, launches agent
/aigon:feature-start 07
# 4. Agent implements the spec...
# → reads spec, explores codebase, writes code
# → commits, writes implementation log
# → signals "submitted" when done
# 5. Merge to main
/aigon:feature-close 07Each step moves the feature through the pipeline: inbox → backlog → in-progress → done.
What’s next
- Drive Mode — hands-on implementation with one agent
- Fleet Mode — multiple agents competing in parallel
- Autopilot Mode — hands-off autonomous loops
- Execution Modes — Drive, Fleet, Autopilot, and Swarm