Bug: IDE Sub-agent (Composer 2.5) Forcibly Uses Fast Mode Despite User Setting

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

I configured the sub-agent option in Cursor settings — I selected Composer 2.5, used edit mode, and turned off fast mode. However, when I use Opus 4.8 to do planning, the sub-agent still chooses Composer 2.5 - fast, which causes my usage to burn like crazy.

Steps to Reproduce

Use Opus 4.8 making plan.

Expected Behavior

Sub-agent Use Composer 2.5

Screenshots / Screen Recordings

Operating System

MacOS

Version Information

Version: 3.7.19 (Universal)
VS Code Extension API: 1.105.1
Commit: 80c653c2c3528e65016a0d304b54486084b470b0
Date: 2026-06-07T01:42:56.126Z
Layout: editor
Build Type: Stable
Release Track: Default
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
xterm.js: 6.1.0-beta.256
OS: Darwin arm64 24.6.0

For AI issues: which model did you use?

Opus 4.8

Does this stop you from using Cursor

No - Cursor works, but with this issue

@Gopher thanks for starting a separate thread, it’s easier to track the IDE case separately from the CLI report.

Confirmed, this is the same known bug, but on the IDE side. The subagent gets resolved to composer-2.5-fast, even though settings have regular Composer 2.5 selected and fast mode is turned off.

There isn’t a reliable workaround on the IDE side right now, because the bug is that the subagent model selection in settings isn’t respected. If you’re using custom subagent definitions with YAML frontmatter, you can try explicitly setting model: inherit so the subagent inherits the parent model, but for built-in subagents when planning on Opus 4.8 this won’t guarantee the result.

One request, if you can, please send the Request ID from the session where the subagent switched to fast Chat menu in the top right > Copy Request ID. This will help with debugging.

For the usage that got billed as fast due to this bug, email [email protected] and they can check it on your account.

I’ll post an update in this thread once there’s a fix.