Explorer agent using Fast instead of normal ($$$)

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

When doing big tasks since the grok or gpt5.6 release, the explorer agent is using the Composer Fast variant even though the non-fast variant is selected, costing much more token than intended.

Steps to Reproduce

  • select sol 5.6 extra high
  • do a big task that requires explorer sub-agents
  • see the explorer showing the fast version (also in the usage dashboard confirmed)

Expected Behavior

The exact model config chosen in the options menu for the explorer should be used.

Screenshots / Screen Recordings

Operating System

Windows 10/11

Version Information

Version: 3.10.20 (user setup)
VS Code Extension API: 1.125.0
Commit: 23b9fb205fe595ea2be29da7214e19762d037fc0
Date: 2026-07-07T07:03:33.071Z
Layout: IDE
Build Type: Stable
Release Track: Default
Electron: 40.10.3
Chromium: 144.0.7559.236
Node.js: 24.15.0
V8: 14.4.258.32-electron.0
xterm.js: 6.1.0-beta.256
OS: Windows_NT x64 10.0.26200

For AI issues: which model did you use?

sol 5.6 extra high
explorer is set to composer 2.5 (NOT FAST)

Does this stop you from using Cursor

No - Cursor works, but with this issue

Hi @alix Thank you for raising this and providing the clear screenshot, we’ve got a bug report raised for this and we will keep you updated on the status of it. Thank you!

Hi @alix — thanks for your patience. The Explore subagent picker could display a model as if it were pinned while it was still on the default, and that default can run the Fast variant. The latest stable release labels that default clearly. We’re still tracking the case where Explore runs Fast even after you explicitly choose standard Composer, so updating may not change the token spend on its own.

If you can, please update, set Explore to standard Composer with Fast off, run a larger task, and check the usage dashboard. If it still shows Fast, reply here and we’ll keep going. Thanks again for the clear report.