Synopsis
aigon feature-eval <ID> [--agent=<id>] [--allow-same-model-judge] [--force]Shortcuts
/afe(slash command) ·aigon afe(CLI)
Flags
| Flag | Description |
|---|---|
--agent=<id> | Force a specific evaluator agent instead of auto-selection |
--allow-same-model-judge | Allow the evaluator to be the same model as an implementer |
--force | Re-run evaluation even if a winner has already been recorded |
Description
feature-eval is the Fleet mode judging step — it compares all agent implementations against the spec, picks a winner, and records that decision so feature-close knows which branch to merge. Run it from the main repo after all agents have signalled submitted.
By default, Aigon auto-selects an evaluator that is different from the implementing agents to avoid bias. Pass --agent=<id> to override and choose a specific evaluator. To allow the same model to judge its own implementation (not recommended), use --allow-same-model-judge.
In Drive mode (single agent), use feature-code-review instead — there is no competition to judge.
What it does
- Reads all submitted implementations from the feature’s worktrees
- Selects an evaluator (or uses the one specified via
--agent) - Opens an evaluation session pre-loaded with the full diff for each agent
- Evaluator compares implementations against the spec’s acceptance criteria
- Records the winner in workflow state
- Suggests
feature-close <ID> <winning-agent>as the next step
Examples
# Auto-select an evaluator and compare
aigon feature-eval 42
# Force a specific evaluator
aigon feature-eval 42 --agent=gg
# Re-evaluate after changing your mind about the winner
aigon feature-eval 42 --forceAfter evaluation
# Merge the winner
aigon feature-close 42 cc
# Merge winner and adopt selected pieces from losers
aigon feature-close 42 cc --adopt ggRelated
feature-code-review— Drive mode alternative: one reviewer inspects and fixesfeature-close— merge the winner after evaluationfeature-autonomous-start— runs eval automatically (AutoConductor)- Fleet Mode guide
Last updated on