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

Aperta
#36,153 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
1-2 giorni
Idoneità per principianti
55/100
Tipo di issue
Bug
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
typescript

Direzione di ricerca

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.

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

Descrizione

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.

Lingua principale
TypeScript
Stelle
24.8k
Fork
6.4k
Merge medio
59m
PR unite (30g)
418

Preparare l'ambiente

Apri in Codespaces

Avvia il container di sviluppo del progetto nel browser, con il tuo account GitHub.

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

Tutte le issue di pingdotgg/t3code

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.