Cursor-Agent spawning subagents of models i did not select?

Support Help
, ,
15

Hey @r-abe, thanks for raising this. The situation is the same as in my update above: subagents can still start on a model you didn’t choose. We’re tracking this issue, and I’ve passed along your point that the impact is more noticeable with the new billing setup. I can’t give an ETA yet, but I’ll post here when there’s an update.

Until there’s a fix, the best workaround is this:

  • Hook subagentStart: Hooks | Cursor Docs
    It receives subagent_model and can return deny for any model you don’t want to allow. This works in the IDE, CLI, and Cloud Agents if you add it to .cursor/hooks.json in the repo.
  • CLI: in /config for cursor-agent, there’s Explore Subagent Model. Set it to Inherit from parent or Disabled. This only covers Explore subagents.
  • Spending cap: set a spending limit so unexpected runs don’t turn into uncapped charges: Usage-based charges | Cursor Docs

You can check which models were used and how charges were applied in Dashboard > Usage. Current pricing is here: Models & Pricing | Cursor Docs. If you want help reviewing specific charges, email [email protected].