Unable to spawn Grok 4.7 and Gemini 3.8 Flash subagents

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

I’m unable to spawn subagents with either Grok 4.7 or Gemini 3.8 Flash — it always falls back to auto without asking anything. And it’s not only a UI badge — the underlying model is clearly Composer.

However it works fine with Grok 4.6 and Opus 5.5.

I have the quota for sure, the models are in “allowlist” and can run direct chat sessions with the mentioned models without any problems. But it doesn’t work when using the Task() tool.

Steps to Reproduce

Spawn a subagent with either Grok 4.7 or Gemini 3.8 Flash model, using explicit model slug directly or specified in .cursor/agents/test.md frontmatter — doesn’t matter since it doesn’t work as expected in both cases.

Expected Behavior

The specified model is always respected.

Operating System

MacOS

Version Information

Version: 3.20.21
VS Code Extension API: 1.128.0
Commit: f09fca384ceca23f7bf21f9c23655b162641d740
Date: 2026-09-13T19:02:51.781Z
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: Darwin arm64 25.6.0

Does this stop you from using Cursor

Yes - Cursor is unusable

Hey @kir, thanks for the report!

This is a known issue we’re already tracking, and I’ve added your report to it. Right now, local subagents set to Grok 4.7 or Gemini 3.8 Flash get started on Auto instead, whether the model comes from the Task call or from an agent file’s frontmatter. Opus 5.5 and Grok 4.6 aren’t affected, which matches what you’re seeing.

In the meantime, pinning subagents to Grok 4.6 keeps the model you picked (for example model: cursor-grok-4.6-high in your .cursor/agents/test.md frontmatter). Leaving the model unset so it inherits from a Grok 4.7 chat doesn’t help, since that path is affected too. Subagents in Cloud Agents also aren’t affected, if that works for your task.

@Colin Hi! I have the same issue with the newest Claude Sonnet 5.5 on the latest Cursor 3.22.12. Looks like all new models are problematic in this regard except Claude Opus 5.5.

Hey @kir,

This has been addressed on our side and will be rolled out soon if it hasn’t been already. The change covers subagents set to Grok 4.7, Gemini 3.8 Flash, and Claude Sonnet 5.5 starting on Auto instead of the model you picked, so it should take care of the Sonnet 5.5 case you mentioned too.

No app update should be needed for this one (a restart of Cursor is worth a try if it doesn’t kick in right away). Could you give it another try and let me know if your subagents still fall back to Auto?

Hey @Colin, long time no see! thanks for this update, I was in fact coming to check if this was adressed or not, I will try it right now and tell you about the results!

yup, seems all fixed!