Agent Task subagents spawn on Fable/GPT without user requesting those models

Hey there!

You’re actually seeing two separate things, and only one is a bug:

  1. Task subagents running on models you didn’t pick (Fable/GPT) is a known bug. When the agent spawns parallel Task subagents it can choose a model on its own instead of inheriting your Grok 4.5 parent, and it sometimes reaches for premium slugs unprompted. We’ve had several reports of this and the team is actively looking into the subagent model-selection behavior — no fix has shipped yet.

  2. “Switched to composer-2.5 after reaching API limit” is expected, not a silent re-route. Once you hit your usage limit, Cursor falls back to an included first-party model (Composer) so the session can keep going. The unrequested premium subagents in #1 are what burn usage quickly, which is what tripped the limit here.

Until the fix lands, the most reliable lever is to pin the model explicitly for your Task subagents instead of leaving it to the agent - e.g. set model: inherit (or a first-party model like composer-2.5) in the subagent/Task calls in your /janitor skill. An explicit model is respected; toggling models off in Settings won’t reliably stop subagents from selecting them. In the meantime, you can watch the subagent cards and cancel any that spin up on a model you didn’t want.

Model field details: Subagents → Model configuration

(@durden - the “terminated but still running” part you hit is a separate known issue; good to keep that one in your own thread so we can track it there.)