Why race teams
For a hard or ambiguous ticket, the cheapest way to get a great result is often to generate more than one and choose. Compete Mode makes that a first-class action: two teams take the same brief from independent angles, and you ship the better outcome.
It’s the diversity that a single deterministic run can’t give you — without you having to manually rerun and babysit a second attempt.
How it works
Mark an issue for competition (a forge-teams: body marker, or compose it in the dashboard) and Forge fans out two parallel pipelines on the same issue. Each team runs its full set of characters
end to end and opens its own PR on its own branch. When both finish, you get a side-by-side view: two diffs, two sets of handoffs, two audit trails.
You pick the winner and record why. The decision feeds back into each character’s success/failure memory and XP, so Compete Mode isn’t just a one-off bake-off — it’s a signal that makes future runs better.
When to use it
- High-stakes or ambiguous tickets where the right approach isn’t obvious up front.
- Evaluating characters or presets against each other on real work.
- De-risking a big change by seeing two independent implementations before you commit.