run: with no model configured, each phase inherits Claude Code's user-level `model` and the run header says nothing about it
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 3/5
- Tiempo estimado
- 1-2 días
- Aptitud para principiantes
- 42/100
- Tipo de issue
- Nueva funcionalidad
- Claridad
- Bien especificado
- Estado de actividad
- Activo
- Stack tecnológico
- typescript
- Área
- devtools
Línea de trabajo
Start with drivers/claude-code.ts around line 165, where the model is spread into the driver config only when config.model is set, then find where the run header is printed. The change is to print the resolved model per phase and label phases that inherit from Claude Code settings. Done when the header and summary show the model for each phase and a run with no model configured says it is inherited.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
What happens
sequant run <issue> --phases spec,exec,qa with no --models, no modelLadder and no model in .sequant/settings.json passes no model to the driver. drivers/claude-code.ts:165 spreads ...(config.model ? { model: config.model } : {}), so the Claude Code process picks its own default, which is the model key in ~/.claude/settings.json. The run header prints Phases, Mode and Issues and no model. The only record is the per-phase model field in the run log (#1198).
Evidence (sequant 2.20.0 at 31c6f8bd, a 30-run batch on a private mirror, 2026-11-02 to 2026-11-03)
The owner's ~/.claude/settings.json changed at 00:12 CST on 2026-11-03 (file mtime), between two runs of the same batch. From the run logs' phases[].model:
- #1143 F1–F5 and #1144 F1–F5 (started 16:50 to 22:26 CST on 11-02): every phase
claude-opus-5-5. - #1153 F1–F5 (started 02:30 CST on 11-03 and later): every recorded phase
claude-fable-5-1; in F3, F4 and F5 the exec field isnullbecause the phase hitphaseTimeoutand the driver reported nomodelUsage, and the transcripts'modelfields areclaude-fable-5-1throughout (305 to 593 messages per run). - The pilot the day before: #1143's F run on Fable, the other five on opus.
Nothing in the batch's stdout shows the change. The two groups differ in cost (opus runs $4.18 to $12.62; Fable runs $4.48 to $46.93 by the SDK estimate) and in how often they hit phaseTimeout (opus 0 of 10, Fable 3 of 5), so a comparison across them is a comparison of models, which the run output does not say.
Ask
- Print the resolved model for each phase in the run header (
Models spec=… exec=… qa=…), and when a phase has no configured model, say so:exec: inherited from Claude Code settings (claude-fable-5-1). - Put the same line in the summary table or the final
Log:block, so a log read after the fact carries it without opening the JSON. - Optional: a
run.requireModelsetting (default off) that refuses to start a phase with no configured model, for benchmark and replay use.
Why it matters
A run's model is the largest single cost and behaviour variable, and today it can change between two issues of one batch with no trace outside the run log. #1198 made the record exist; this is about making it visible at the time.
From a private replay study of sequant on our own repos; raw runs are not public. Filed by the owner.
- Lenguaje dominante
- TypeScript
- Estrellas
- 1
- Forks
- 1
- Merge medio
- 10 h 59 min
- PR fusionados (30 d)
- 86
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Sin plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de sequant-io/sequant
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 83/100
sequant-io/sequant#1665 ·
Los mantenedores suelen responder en 1 día
-
fix(assess): minimal-flags rule still assumes a ui label adds the test phase (stale after #1649)Abierto
Dificultad 1/5 1-3 horas Aptitud para principiantes 87/100
sequant-io/sequant#1662 ·
Los mantenedores suelen responder en 1 día
-
graph-2026-11-simplify
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
sequant-io/sequant#1650 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
sequant-io/sequant#1601 ·
Los mantenedores suelen responder en 1 día
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 86/100
sequant-io/sequant#1582 ·
Los mantenedores suelen responder en 1 día
Todos los issues de sequant-io/sequant
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 73/100
Los mantenedores suelen responder en 1 día
-
area/admin/user area/internationalization automated-triage issue/auto-triaged type/bug
Dificultad 1/5 Menos de una hora Aptitud para principiantes 76/100
grafana/grafana#137281 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
accessibility bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 79/100
Luen/crag-stats#429 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 88/100
Los mantenedores suelen responder en 1 día
-
Missing assertions to legacy Cafe Menu block testsPosiblemente ocupada @mariamanbar la tomó hoy. Abierto
Dificultad 1/5 Menos de una hora Aptitud para principiantes 90/100
freeCodeCamp/freeCodeCamp#71624 ·
Los mantenedores suelen responder en 1 día