Skip to content

feat(auto-routing): classify intent before choosing a model - #560

Open
astyfx wants to merge 1 commit into
mainfrom
fix/autorouter-intent-classifier
Open

astyfx wants to merge 1 commit into
mainfrom
fix/autorouter-intent-classifier

Conversation

@astyfx

@astyfx astyfx commented Sep 18, 2026

Copy link
Copy Markdown
Member

Summary

Auto now asks the configured Utility model to classify intent before choosing the execution model. Existing profiles migrate to model-first routing while preserving custom rules; explicit opt-out on the new profile version remains supported. Auto itself remains opt-in.

  • Use bounded, validated intent, complexity, risk, and continuity results with deterministic capability floors and eligible-model constraints.
  • Simplify preferences and default rules while preserving advanced customization and capable-model continuity.
  • Add a cancellable 30-second classification deadline, progress and fallback notices, isolated ephemeral Codex threads, and bounded result/readiness caches.

Validation

  • 374 focused tests passed across 18 files, covering routing, migration, cancellation, isolation, cache behavior, provider runtime, settings, and themes.
  • Desktop build, documentation path checks, and diff whitespace checks passed.
  • Three live Luna classifications selected Luna for bounded explanation/edit requests and Astra for a high-risk continuation, without heuristic fallback.
  • Narrow light/dark layout measurements showed no horizontal overflow. Screenshot verification timed out; full repository tests were not run.

Remaining limitation

Live classification took 7.5–17.3 seconds before primary execution. The longer deadline makes model-first classification usable; it does not eliminate model latency. Cancellation prevents the primary turn from starting, and classification failures explicitly fall back to local routing.

@astyfx
astyfx requested a review from a team as a code owner September 18, 2026 13:46
@astyfx
astyfx requested review from JongSikLim and schang124 and removed request for a team September 18, 2026 13:46
@upwind-code-us

upwind-code-us Bot commented Sep 18, 2026

Copy link
Copy Markdown

Upwind Upwind Code Scan - ✅ Passed

0 newly introduced vulnerabilities · 0 resolved · 57 total in this PR vs main

Total breakdown: 🔶 6 High | 🟡 48 Medium | 🟢 3 Low

View full analysis in Upwind Console

Scan completed in 17s

Scan history (1 scan)
Commit Scanned at New Resolved Net
83d62b7 < 2026-09-18 13:47 UTC 0 0 0

Last scanned: 83d62b7 · 2026-09-18 13:47 UTC

@upwind-code-us

upwind-code-us Bot commented Sep 18, 2026

Copy link
Copy Markdown

Upwind Upwind IaC Scan - ✅ Passed

0 newly introduced misconfigurations · 0 resolved · 0 total in this PR vs main

View full analysis in Upwind Console →

Scan completed in 1s

Scan history (1 scan)
Commit Scanned at New Resolved Net
83d62b7 < 2026-09-18 13:47 UTC 0 0 0

Last scanned: 83d62b7 · 2026-09-18 13:47 UTC

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant