Cascade routing core: two-model user selection + escalate-on-gate-failure flow
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- typescript
Research direction
Start with parent #1134 and the verification-gate subtask, then trace the config schema, CLI flags, interactive picker, session-start validation, and TUI/status-line entry points. Add tests for config validation, escalation after gate failure, no escalation after a pass, and unattended attempt counts; done means both user-selected providers validate and every routing decision is surfaced.
Written by the indexing model from the issue text.
Description
Parent: #1134
Implement the routing core:
- Config schema:
route.mode: "cascade",route.primary: "<provider/model>",route.escalation: "<provider/model>",route.primary_attempts(default 1 interactive, 3 unattended). - Both models are USER-SELECTED (config file, CLI flags, and interactive picker); validate both are configured providers at session start; clear error if not.
- Flow: run task on primary → on verification-gate failure (see gate subtask) escalate: restart the task on the escalation model, carrying the task prompt and a compact failure summary (what the gate rejected), NOT the full failed transcript.
- Session UX: routing decisions surfaced in the TUI/status line ("primary: X", "escalated to Y: build failed"), never silent.
- Tests: config validation, escalate-on-failure, no-escalate-on-pass, unattended attempt count.
- Dominant language
- TypeScript
- Stars
- 813
- Forks
- 134
- Avg merge
- 1d 18h
- Merged PRs (30d)
- 59
Getting set up
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from AltimateAI/altimate-code
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
AltimateAI/altimate-code#1378 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
AltimateAI/altimate-code#1359 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
AltimateAI/altimate-code#1323 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
AltimateAI/altimate-code#1288 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
AltimateAI/altimate-code#1285 ·
Maintainers usually reply within 1 day
All issues in AltimateAI/altimate-code
Similar issues
-
triage
Difficulty 1/5 Under an hour Newbie friendliness 90/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
mermaid-js/mermaid-live-editor#2053 ·
Maintainers usually reply within 1 day
-
factory
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
jessepollak/home#1455 ·
Maintainers usually reply within 1 day
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 95/100
lingdojo/kana-dojo#31227 · 1 comment · 5 reactions ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
appandflow/stim#1838 ·
Maintainers usually reply within 1 day