Closed Help thread 166082 already has this error from July. I hit it again today in the Cursor IDE Task tool, 17 Sep 2026, not CLI.
I set the Task model to composer-2.5. Rejected. I retried the same call unchanged. Rejected again. The allowed list returned one slug: composer-2.5-fast.
A grok 4.6 model (cursor-grok-4.6-high) was accepted in the same session after I named it in chat.
Please treat composer-2.5 as a valid inline Task slug, not only the fast variant.
OS: Windows 10.0.26200
Cursor: 3.20.21 (f09fca384ceca23f7bf21f9c23655b162641d740)
Request ID: 2227871c-3eba-43c1-ae41-7330e131ace7
Invalid model selection “composer-2.5”. Model could not be resolved to a valid subagent model.
Allowed model slugs:
composer-2.5-fast
Related open bug (CLI/SDK whitelist, same one-slug shape):
Steps to Reproduce
I set the Task model to composer-2.5. Rejected. I retried the same call unchanged. Rejected again. The allowed list returned one slug: composer-2.5-fast.
Expected Behavior
Please treat composer-2.5 as a valid inline Task slug, not only the fast variant.
Hey @Olivier_Berthet1, thanks for the detailed report and for linking the earlier thread.
You’re reading the behavior right: the inline model list for Task mirrors your model picker with one variant per model family, and Composer 2.5 defaults to Fast, so only composer-2.5-fast shows up. This is a known limitation the team is tracking, and I’ve added your report to it.
Two ways to get standard Composer 2.5 subagents today:
In the model picker, select Composer 2.5 and turn Fast off, then start a fresh chat. composer-2.5 will then appear in the allowed list alongside composer-2.5-fast.
Define a custom subagent (for example .cursor/agents/composer-standard.md) with model: composer-2.5[fast=false] in the frontmatter and dispatch it by name. The bracket syntax is honored there, just not in the inline Task parameter.