Setting an explorer agent doesnt work

Support Bug Reports
, ,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Bug: In Planning Mode, the Explorer agent always uses Composer 2.5 instead of the model configured in Settings (Claude Sonnet).

Expected behavior:

  • Explorer should use the model selected in Settings.

Actual behavior:

  • Explorer is automatically assigned Composer 2.5.
  • This results in additional request consumption.
  • My usage limit is reached faster because requests are being spent on a model I did not choose.

Please confirm whether this is a bug or intended behavior. If intended, it should be clearly documented, as it has a direct impact on request usage and quota consumption.

Steps to Reproduce

set in settings the desired model → try to plan with explorer agents

Expected Behavior

Explorer should use the model selected in Settings.

Operating System

Windows 10/11

Version Information

Version: 3.7.36 (user setup)
VS Code Extension API: 1.105.1
Commit: 776d1f9d76df50a4e0aeca61819a88e7c1b861e0
Date: 2026-06-13T00:31:56.287Z
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: Windows_NT x64 10.0.26200

For AI issues: add Request ID with privacy disabled

8412ca38-a78b-4cf2-803b-99886fc1a6c4

Does this stop you from using Cursor

No - Cursor works, but with this issue

5

Hey there.

It looks like you’re on legacy, request-based pricing. On this pricing, you must enable Max Mode to use subagents that are not Composer. See the FAQ here.

7

that’s weird, why do I have the option to change it with no warning or something then?

8

It will change the subagent model if you enable Max Mode in a conversation!

Heard that this could be more obvious for users on request-based plans.