[Bug]: Factory Droid (ACP Registry) shows reasoning effort only for its default model since #35458

Abierto
  • ¿Algo no está bien?
#36,153 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
1-2 días
Aptitud para principiantes
55/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
typescript
Área
backend-api-design

Línea de trabajo

Start in the apps/server area and read the changes in #35458, which the issue identifies as the regression. Reproduce with Factory Droid through the ACP Registry, comparing the reasoning-effort options for the default Sonnet 5.5 model and non-default Opus 5.5 or GPT-6.1 Sol. Done when each model shows the reasoning-effort levels Droid reports, without options leaking between models.

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

Descripción

Before submitting
  • I searched existing issues and did not find a duplicate.
  • I included enough detail to reproduce or investigate the problem.
Area

apps/server

Steps to reproduce
  1. Set Droid's default model to Sonnet 5.5 (sessionDefaultSettings.model: "claude-sonnet-5-5" in ~/.factory/settings.json).
  2. Start T3 Code nightly 0.1.10-nightly.20261113.4630 with Factory Droid added through the ACP Registry.
  3. In a new thread, pick Factory Droid with Opus 5.5 (or any model other than Sonnet 5.5) and open the model options.
Expected behavior

Opus 5.5 shows a Reasoning Effort picker with the levels Droid reports for it (low, medium, high, xhigh, max), as it did before the update.

Actual behavior

In the composer model picker, Factory Droid's Opus 5.5 and GPT-6.1 Sol show only Autonomy Level. Droid's Sonnet 5.5, the model the startup probe session opens on, shows Reasoning Effort (Off, Low, Medium, High, Extra High, Maximum) plus Autonomy Level.

The provider cache shows the same thing:

  • ~/.t3/caches/acpRegistry_factory_droid.json (checked 2026-11-13): reasoning_effort on 1 of 74 models (claude-sonnet-5-5).
  • Older ~/.t3/caches/droid.json from 2026-10-06, same acpRegistry driver: reasoning_effort on 58 of 59 models.

Droid still reports the option for each model. Driving droid exec --output-format acp directly (initialize, session/new, then session/set_config_option):

  • session/new -> current model claude-sonnet-5-5, reasoning_effort = off/low/medium/high/xhigh/max
  • set model = claude-opus-5-5 -> reasoning_effort = low/medium/high/xhigh/max
  • set reasoning_effort = high -> accepted, current value high
  • set model = gpt-6.1-sol -> reasoning_effort = low/medium/high/xhigh/max

This started with #35458. It keeps model-specific options only for the model that was current in a session. Its "Not in this change" section lists this case: a model that was never current in a session shows no reasoning options. For Droid, the probe always opens on the user's default model, so only that one model gets an effort picker. The fix for #15177 stopped one model's options from leaking to the others, but it also took the effort picker away from every Droid model except one.

Impact

Major degradation or frequent failure

Version or commit

0.1.10-nightly.20261113.4630

Environment

macOS 26.5, T3 Code desktop (Nightly), Factory Droid 1.10.0 via ACP Registry

Workaround

None found in T3. Changing Droid's default model only moves the picker to that one model.

Written with Claude Opus 5.5 in Factory Droid. The initial investigation was done with GPT-6.1 Sol in Codex.

Lenguaje dominante
TypeScript
Estrellas
24.8k
Forks
6.4k
Merge medio
59 min
PR fusionados (30 d)
418

Preparar el entorno

Abrir en Codespaces

Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.

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 pingdotgg/t3code

Todos los issues de pingdotgg/t3code

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.