Allow per-stage model and reasoning selection

Abierto
#29 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
48/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
typescript

Línea de trabajo

No files, tests, or entry points are named. Start by locating the existing global model and reasoning configuration and the plan, packet review, verification, and composition stage dispatch. Done means stages can override either setting through the proposed configuration while unnamed stages retain the global defaults, with coverage for fallback behavior.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Problem

One model and one reasoning effort apply to every stage of a run. Stage 7 (packet review) dominates the token spend, so the strong model is paid for on work that does not need it.

Measured across runs of 0.5.6 on diffs of 9, 40 and 96 hunks (run.json / telemetry token counts):

stage share of total tokens
planning 1-2%
packet review 85-93%
verification 5-15%

Totals scale with the diff: ~0.9M tokens for 9 hunks, ~4.1M for 40, ~8M for 96. The Anthropic lane at opus/high reasoning uses about 1.7x the tokens of the openai-codex lane for the same diff.

Because the model is global, the only cost control available is to downgrade the packet review as well, which is the one stage where quality is the product.

Proposal

Allow the model and the reasoning effort to be selected per stage, falling back to the current global setting when a stage is not named:

[llm]
model = "..."            # default, unchanged

[llm.stages.plan]
model = "<cheaper model>"
reasoning = "low"

[llm.stages.verify]
reasoning = "medium"

Planning and composition look like the clear candidates for a cheaper model: they are structural work over text the pipeline already produced, and they are 1-2% and a few percent of the spend respectively. Verification is the interesting middle case - it is the main false-positive filter, so the value of a separate knob there is that it can be measured rather than assumed.

Why it matters

Per-stage selection turns "which model do I trust with this repository" into a per-stage question with a measurable answer, instead of one global decision that is paid for on every packet. It is also the prerequisite for anyone to publish a cost/quality curve for the tool.

Related but independent: #11 (grouping more related hunks) reduces the number of packet calls. The two levers compose - fewer calls, and the right model per call.

Happy to test a branch against a range of diff sizes and report tokens, wall time and finding deltas per stage.

Lenguaje dominante
TypeScript
Estrellas
8
Forks
1
Merge medio
5 min
PR fusionados (30 d)
2

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de 0xPolygon/codegenie

Todos los issues de 0xPolygon/codegenie

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.