Skip to content

Adaptive routing memory: learn task-class priors from outcomes #1137

Closed as not planned

Description

@anandgupta42

Parent: #1134

Learn from mistakes — adaptive routing memory:

  • Persist per-task-class outcomes locally (class → primary attempts, gate passes, escalations). Task class = coarse heuristic (e.g. task-type keywords, project size bucket), not prompt text.
  • Routing consult: classes whose primary success rate is below a threshold (default e.g. <20% over ≥5 samples) skip the primary and go straight to escalation; surfaced in the session UX ("skipping primary: this task class escalated 9/10 recent runs").
  • User control: view (route report includes the memory), reset, and disable (route.adaptive: false).
  • Keep it transparent and simple: counts and thresholds, no opaque scoring in v1.
  • Tests: threshold behavior, decay/window, reset, disable.

Activity

  1. changed the title [-]Cascade measurement: routing telemetry, session summary, aggregate report[/-] [+]Adaptive routing memory: learn task-class priors from outcomes[/+] on Aug 24, 2026
  2. anandgupta42 commented on Nov 5, 2026

    @anandgupta42
    ContributorAuthor

    Closing: after evaluating verifier-gated and cascade routing, we decided not to build an inferred per-request router. The direction is a strong default model with explicit, user-chosen modes. Reopen if routing is revisited.

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions