Hey, thanks for the detailed write-up and the screenshot. On your three questions:
No. grok-bot-default and grok-bot-automation don’t count against your monthly Cursor Models quota. Grok Bot chats and automations are metered against Grok Bot’s own weekly allowance, which isn’t tied to your Cursor plan. The only exception is cloud coding agents that Grok Bot runs for you. Those count against your Cursor plan like any other cloud agent. You don’t have any of those runs.
They show up there because of a display issue we’re already tracking. The per-model breakdown under Cursor Models isn’t filtering out Grok Bot rows yet, so they appear in the list and take up part of the percentage. The 23.1% header is correct and reflects only your real usage in the Cursor app. Only the rows under it are labelled wrong.
No. Grok Bot usage won’t reduce your remaining Composer or Cursor Grok model quota. The only way Grok Bot touches your Cursor plan is via the cloud agent case in point 1.
Nothing needs fixing on your account. Once the breakdown is corrected, the grok-bot rows will disappear from that list, and your own Cursor model percentages will increase up to the same 23.1% (the header will stay the same). I’ll reply here if there’s an update.
Thanks for the detailed explanation, Dean. This clears up my confusion about the Grok Bot usage display issue.
By the way, I’m a new Cursor user and I’ve been really enjoying Composer 2.5. It has become my preferred model for daily coding because of its speed and coding performance.
I was wondering if there are plans to continue evolving the Composer model line. Composer 2.5 has been available for several months now, and I’m curious whether a future Composer version is currently being developed.
I understand you may not be able to share specific release dates, but I’d love to know whether Composer is still an active focus for the team.
Small update on this thread: the change that removes grok-bot-default and grok-bot-automation from the Cursor Models and Other Models breakdown has been rolled out. Based on your latest screenshot, those rows are already gone on your side.
@alorbach, about the percentage not going down: that’s expected. Grok Bot spend was never charged to your Cursor Models pool. In the breakdown, those rows only took up part of the percentage inside the list, but the header total always reflected only real Cursor usage. So when we removed the rows, there wasn’t any extra usage sitting there and nothing needed to be refunded. Your own model percentages just increased to fill the same header. What you’re seeing now (Cursor Models 70.2%, Other Models 72.0%) is your actual Cursor usage, and it hasn’t changed.
Grok Bot is still metered against its own separate weekly allowance, separate from the Cursor plan. The only exception is cloud agents that Grok Bot runs on your behalf, those go on the Cursor plan like any other cloud agent.
If after a day or two you still see grok-bot rows in the breakdown, or something doesn’t add up, send a screenshot and we’ll take a look.
but it didn’t 
