Unexpected gpt-5.6-sol-medium usage (~74% of Other Models budget) from Task sub-agents I did not select

Support Bug Reports
, ,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Summary
I did not manually select GPT-5.6 Sol. On 2026-09-23, three large usage entries appeared under gpt-5.6-sol-medium and consumed a large share of my Other Models budget (≈74%). Local agent transcripts show these were Task sub-agents spawned by the parent agent with an explicit model: “gpt-5.6-sol-medium”.

Usage UI (screenshot)

2026-09-23, 12:42 PM — gpt-5.6-sol-medium — ~3.6M
2026-09-23, 12:42 PM — gpt-5.6-sol-medium — ~5.1M
2026-09-23, 12:43 PM — gpt-5.6-sol-medium — ~3.4M
All marked Included.
(If the dashboard timestamps are UTC, that matches ~14:42–14:43 local UTC+2.)
Local evidence

Composer / chat ID: 2bf78e3c-d254-4653-9765-581729ae58e2

Shortly after, the parent agent issued three parallel cursor → Task calls (CallDynamicTool, toolName: “Task”, subagent_type: “generalPurpose”, run_in_background: true), each with:

model: “gpt-5.6-sol-medium”
Descriptions:
Port pine 0053-0055,0057
Port pine 0058-0064
Port pine 0066-0069
Project context: offline Pine→Python ports in C:\Users\sebas\Desktop\Trading\perp-backtest.

Across local transcripts, this appears to be the only real launch of gpt-5.6-sol-medium (other “sol” hits are just the system model list).

Steps to Reproduce

I have no control over it

Expected Behavior

Only the model I had selected for the chat (Auto / non-Sol). I never chose Sol in the model picker and was unaware sub-agents could bill Sol under Other Models.

Operating System

Windows 10/11

Version Information

Version: 3.21.16 (user setup)
VS Code Extension API: 1.128.0
Commit: 8ae78e8eee1e63479c7e0504b664bc0a80c68000
Date: 2026-09-19T06:43:22.276Z
Layout: IDE
Build Type: Stable
Release Track: Default
Electron: 42.10.0
Chromium: 148.0.7778.280
Node.js: 24.18.1
V8: 14.8.178.38-electron.0
xterm.js: 6.1.0-beta.291
OS: Windows_NT x64 10.0.26200

For AI issues: which model did you use?

Auto in the Chat, Sol was chosen automatically.

Does this stop you from using Cursor

No - Cursor works, but with this issue

5

Hey, thanks for the detailed report with the chat ID and transcripts. It really helps.

This is a known issue we’re tracking. When the main agent hands work to a sub-agent via Task, it can pass a specific model for that sub-agent (in your case GPT-5.6 Sol), and right now that overrides your Auto inheritance. By default, sub-agents should inherit the model you selected. The team is working on stricter controls over which models sub-agents can use, but there’s no exact timeline yet.

What helps right now:

  1. Turn off GPT-5.6 Sol (and any other models you don’t want to pay for) in Cursor Settings > Models. In the IDE, this also removes the model from the list a sub-agent can start on.
  2. Add a User Rule in Cursor Settings > Rules: “When spawning subagents with the Task tool, never pass a model parameter. Subagents must always inherit the parent model unless I explicitly ask for a different one.”

For the charges for those three sub-agent runs from 2026-09-23: email [email protected] from the email on your account and include the chat ID you already shared. The team can review your case.

Let me know if the sub-agent still starts on Sol after you disable it.