Mismatch on sub-agent model for execute plan

Hello guys. I have been created a plan on “project”, the model for the project is opus 5.5.
But even if I choose to build the plan with grok 4.7, it still spawning sub-agent in the project with opus 5.5 instead of the selected model. It burns out tons of my token for 3rd party model. I am not sure if this is an issue to be fixed or not. Thanks for helping

Hey, thanks for the report. You’re right, this shouldn’t happen, and it’s not something in your setup.

Right now, in a Project, a scheduled Build uses the Project’s main chat model, and any agents it spawns inherit that model. That’s why you saw Opus 5.5 instead of the Grok 4.7 you selected. I passed this to the team, and it’s a known issue we’re tracking.

Until it’s fixed, here’s how to get a build on Grok 4.7:

  1. Open the Project’s main chat Weather Board.
  2. In the model picker at the bottom of that chat, select Grok 4.7 Extra High.
  3. Open the plan and click Build.
  4. Open the new agent that starts, then check its model picker. It should show Grok 4.7.
  5. After that, you can switch the Project’s main chat back to Opus 5.5 if you want Opus for planning.

If the agent is already running on Opus, switch its own model picker to Grok 4.7, and it’ll apply to the next message.

On token usage for the selected model, if you want the team to look at your specific usage, email [email protected]. A separate team handles that.

Let me know if the workaround worked.