Skip to content

docs(blog): add stall-escalation solve-rate result #1214

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
moe-berri wants to merge 2 commits into
base: main
Choose a base branch
from
+2 −0
Open

docs(blog): add stall-escalation solve-rate result #1214

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
79e575e
docs(blog): add stall-escalation solve-rate result
moe-berri Sep 5, 2026
d68bfc1
Update index.md
moe-berri Sep 5, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions blog/autorouter_stall_escalation/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -31,6 +31,8 @@ A cheap model can get stuck mid-task: it calls the same tool with the same argum

`stall_escalation_enabled: true` gives the router that judgment on its own.

On a 24-task test set escalating `gpt-4.1-nano` to `gpt-5.4-mini`, stall escalation achieved 52.8% solve rate vs 38.9% without it, a 14 percentage point jump. Both models are not that powerful, but the improvement is good proof that it works.

## How it decides

- **Reads the assistant's own tool calls, not the human's messages.** A task counts as stalled once the newest call repeats, or errors, at least `stall_escalation_repeat_threshold` times across the last `stall_escalation_window` calls
Expand Down
Loading