Allow configurable fallback chains for model elevation

Aperta
#1,555 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
35/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Tranquilla
Stack tecnologico
typescript

Direzione di ricerca

Start by tracing the model-elevation workflow and the existing plan_model configuration, then identify where provider availability failures trigger the current inline fallback. Locate the configuration parsing, retry/fallback orchestration, and model-selection reporting paths; the issue names no specific files or tests. Done means an explicitly ordered chain with per-model reasoning effort and fresh-context options is supported, exhaustion behavior is configurable, each attempt and reason is reported, and single-model behavior remains compatible.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Feature request

Allow model elevation to use an explicitly configured, ordered fallback chain when the preferred model is unavailable.

Current behavior

In Compound Engineering 3.23.4, CE Plan accepts a single model through plan_model. If that model cannot complete the elevated step, the workflow eventually falls back to authoring inline with the session model.

For example, I encountered this sequence:

  1. plan_model: fable selected Fable.
  2. The provider reported that the weekly Fable usage limit had been reached.
  3. CE Plan followed its current recovery behavior and continued inline.

That fallback keeps the workflow moving, but it removes the independent model judgment that model elevation was intended to provide.

Desired behavior

It would be useful to configure an ordered list of acceptable alternatives, including the reasoning effort for each one.

For example:

  1. Fable at high
  2. Opus at xhigh
  3. Sol at xhigh, launched as a fresh-context subagent
  4. Stop if none of the configured models is available

The model names should remain aliases such as fable, opus, and sol, allowing the provider or host to resolve the current model generation rather than requiring version-specific IDs.

The exact configuration format is up to the maintainers.

Expected properties

  • Fall back only to models the user explicitly configured.
  • Advance to the next model for clearly identified availability or capacity failures, such as an exhausted usage allowance.
  • Preserve the same read-only evidence and decision bundle across attempts.
  • Allow a fallback candidate to require fresh context so its judgment remains independent from the orchestrating session.
  • Report which models were attempted, why each fallback occurred, and which model and effort ultimately served the request.
  • Allow the user to choose whether total exhaustion falls back inline or stops the workflow.
  • Preserve the existing single-model behavior for users who do not configure a fallback chain.

Why this would help

In unattended or pipeline-driven runs, silently dropping from an independent planning model to the orchestrating session model can materially change the strength of the planning gate.

An explicit fallback chain would preserve the current transparent, user-controlled model-selection philosophy while making temporary provider limits less disruptive.

Lingua principale
TypeScript
Stelle
25.6k
Fork
2.1k
Merge medio
3h 57m
PR unite (30g)
170

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di EveryInc/compound-engineering-plugin

Tutte le issue di EveryInc/compound-engineering-plugin

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.