Main Agent starts as Grok 4.7 High model. It then spawns defined subagents (subagents are defined with model: inherit in .cursor/agents/ folder) to work on delegated tasks. However, when the subagent is spawned:
Main Agent shows the Subagent model name as “Grok 4.7 High”.
Hey @Duong_Do, thanks for the report and the screenshots!
This is a known issue we’re already tracking, and I’ve added your report to it. Subagents that inherit a Grok 4.7 model are currently started on Auto by the desktop app, which is why the subagent tab and your usage page show Auto. So the usage page is accurate: those subagents really ran on Auto.
In the meantime, two things work today:
In your .cursor/agents/*.md files, change model: inherit to a Grok 4.6 option (for example model: cursor-grok-4.6-high). Grok 4.6 subagents run on the model you pick.
If you can run the work as a Cloud Agent, its subagents can already be pinned to Grok 4.7.
About your example, I’m using Grok 4.7 High as the main agent, putting Grok 4.6 into the subagent definition seems unreasonable because they have the same pricing currently, why do I want to use previous model if they have the same price?
Anyway, please help prioritize this issue because it does affect how our designed workflow runs. Sometimes we notice the workflow runs for an unexpectedly longer period, or the output of subagents is sometimes low in quality, then we check and realize that the subagents were running on Auto. We then need to discard that run because of the quality while the usage is still being recorded, wasting token and money.
More on this issue: the subagent model set is not working with custom API model also.
In the following session, I’m using custom LLM API Key where the Main Agent is set to use Grok 4.7 and subagents use Grok 4.6. At the end all spawned subagents were using Grok 4.7 instead of 4.6.
Thanks for your patience on this. A fix for inherited Grok 4.7 subagents starting on Auto has now been rolled out on our side, so no Cursor update is needed. Subagents with model: inherit under a Grok 4.7 parent should now run on Grok 4.7, and your usage page should show them that way.
Could you give your workflow another try and let me know if any subagents still show up as Auto?
The custom API model case from your last post (subagents set to Grok 4.6 running on your Grok 4.7 model instead) is a different path that this fix doesn’t cover. We’re looking at that one separately, and the request ID you shared helps.
