Aigon’s CLI commands are grouped by workflow. Most workflow commands have both a long form (aigon feature-create) and an agent-invoked form (/aigon:feature-create, $aigon-feature-create, or an inlined launch prompt, depending on the agent).

This reference covers the commands users normally run directly. Aigon also has lower-level plumbing commands for hooks, telemetry capture, migrations, and dashboard internals; those remain discoverable through aigon help and source-level docs rather than standalone website pages.

Setup commands

Install, initialize, and repair Aigon.

• setup — Run or resume first-run onboarding
• install-agent — Install agent commands, skills, hooks, and context files
• apply — Initialize repo on first run, then keep Aigon files up to date
• remove — Remove Aigon-managed files from the current repo
• doctor — Detect and repair common project state drift
• seed-reset — Reset demo seed repositories

Feature commands

The core delivery workflow — moving a feature from idea to merged code.

• feature-create — Create a new feature spec in the inbox
• feature-prioritise — Assign an ID and move to the backlog
• feature-start — Create workspace and begin implementation
• feature-do — Implement a feature (Drive or Fleet mode)
• feature-open — Open the feature worktree and start an agent
• feature-code-review — Code-review a feature with a different agent
• feature-code-revise — Implementer-side follow-up after a code review
• feature-eval — Evaluate or compare implementations
• feature-close — Merge the winner and finish the feature
• feature-cleanup — Garbage-collect worktrees and branches
• feature-reset — Full reset: kill sessions, drop worktrees, return spec to backlog
• feature-now — Fast-track: create + prioritise + start in one step
• feature-autonomous-start — Background AutoConductor session
• feature-validate — Run a feature’s validation commands

Research commands

Front-load investigation before you commit to building.

• research-create — Create a new research topic
• research-prioritise — Assign an ID and move to the backlog
• research-start — Create workspace and begin research
• research-do — Have an agent investigate and write findings
• research-open — Open Fleet research agents side-by-side
• research-eval — Synthesize findings and recommend features
• research-autopilot — Fleet research + spawn + monitor + evaluate
• research-close — Move finished research to done

Feedback commands

Capture and triage incoming feedback before it becomes a feature.

• feedback-create — Create a new feedback item
• feedback-list — List feedback items with filters
• feedback-triage — AI-assisted triage with recommendations

Infrastructure commands

The dashboard, server, and supporting tooling that runs around your features.

• board — Show the Kanban board (or list view)
• server — Manage the Aigon dashboard server
• config — Read and write global/project config
• proxy — Manage the optional .localhost proxy
• proxy-setup — Inspect local proxy setup
• dev-server — Manage app dev servers (start, stop, logs)
• status — Show repo status across all workflows
• agent-status — Per-agent status signals (used by hooks)
• sessions-close — Kill all agent sessions for an ID
• session-list — List all live Aigon-managed tmux sessions
• token-window — Nudge sessions to align rolling provider usage windows
• repair — Repair safe drift without resetting work
• next — Suggest the most likely next workflow action
• insights — Pro analytics: cost, quality, trends
• Aigon Sync (Pro) — aigon backup / aigon vault and dashboard Settings → Aigon Sync; see the Aigon Sync guide (CLI reference ships in @senlabsai/aigon-pro)
• deploy — Deploy a feature preview
• help — Show available commands

Pro commands

Commands that ship in the open-source CLI but gate on @senlabsai/aigon-pro being installed and activated. See Installing Aigon Pro.

• pro activate — Save your Pro key to ~/.aigon/config.json
• pro status — Show install / key / activation state
• installed-notice — Post-upgrade summary of which registered repos are behind

Conventions

• Slash form — every workflow command is also a slash command inside Claude Code, Gemini, Codex, and Cursor: /aigon:feature-create, /aigon:research-start, etc.
• Shortcuts — common commands have two-letter aliases (afc for feature-create, ars for research-start, ab for board). See each command page for its shortcut.
• IDs vs names — most commands accept either the numeric feature ID (42) or the feature slug (dark-mode). Aigon resolves whichever you give it.