Solutions · Bug triage
Reproduce first, plan second
Most bug reports are missing something. Triage agents read the code, try to reproduce the problem in a clean worktree, and come back with evidence or a precise question.
What you get back
A reproduction
A failing test or exact steps, committed to the card's branch.
Impact and effort
Labels with the evidence behind them, which you can override.
One clear question
When the code cannot answer it, the agent asks you, not the reporter.
How a bug moves
- 01
Issue arrives
A GitHub issue or feedback card lands in New.
- 02
Investigation
The agent reads related code and recent changes, then tries to reproduce.
- 03
Evidence or question
The card shows a reproduction, or waits for your answer.
- 04
Plan
Only reproduced bugs move to Planning by default.
Spend your time on decisions
Let agents do the digging.