[Bug]: "auto" model always logs as composer-2.5-fast with T3 Code (Cursor integration loses auto model routing)

[KaKi87]

Before submitting

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

Area

apps/desktop

Steps to reproduce

1. Launch T3 Code and connect to Cursor backend.
2. In the T3 Code UI, select the "auto" model and interact with the assistant.
3. Open the Cursor usage logs panel (or relevant log output).
4. Observe that the model is displayed as composer-2.5-fast, not "auto".
5. Repeat the same steps using the official Cursor IDE or JetBrains integration, selecting "auto".
6. Observe that logs show model as "auto" instead of a specific resolved model.

Expected behavior

The usage logs should record "auto" as the model when selected, mirroring Cursor IDE/JetBrains, and should dynamically select among compatible models if possible.

Actual behavior

When using T3 Code, selecting "auto" always logs usage as composer-2.5-fast. There is no way for "auto" to resolve to a different model, nor is the "auto" sentinel preserved in logs. In contrast, Cursor IDE and JetBrains both show the selection as "auto" in logs, which enables dynamic routing and/or future-proofing.

Impact

Major degradation or frequent failure

Version or commit

0.0.24

Environment

T3 Code main branch; macOS; Cursor backend; model composer-2.5-fast; also tested with Cursor IDE/JetBrains integration; see logs for details.

Logs or stack traces

No response

Screenshots, recordings, or supporting files

No response

Workaround

Explicitly selecting Composer 2.5 as a workaround; cannot dynamically route to other models via "auto" in T3 Code.

---

Thanks

[lklynet]

I also have noticed that if I set it to just Composer 2.5, in my cursor usage page i see calls to gpt 5.1 and claude-4-sonnet. there is no way that I can see to set subagents to inherit from parent?

[juliusmarminge]

There seems to be a bug in Cursor ACP model selection: https://gist.github.com/juliusmarminge/65f5a313afcedaffe015716c7b7db13b. I've raised it to their team and will get it fixed upstream