Allow SuperGrok usage limits to be consumed inside Cursor IDE (not only unlock free Ultra)

Feature request for product/service

Cursor IDE

Describe the request

Currently, SuperGrok Heavy subscribers get free Cursor Ultra access, which is great. However, the actual usage limits from the SuperGrok Heavy pool cannot be used inside the Cursor IDE itself.
Heavy limits work in:

grok.com / Grok apps
Grok Build (CLI/TUI)
Grok Bot

But when working in the Cursor editor (Agent, Chat, Composer, etc.), only the Cursor Ultra usage pool is available. The two pools remain completely separate.
Why this would be useful
Many developers who pay for SuperGrok Heavy primarily work inside Cursor (not in the terminal). Right now they get the “free Ultra” benefit, but cannot actually spend their expensive Heavy limits where they spend most of their time — in the IDE.
It would be much more natural and valuable if SuperGrok Heavy usage could also be consumed (or shared) when using Grok models inside Cursor.
Suggested behavior

Option to draw from SuperGrok Heavy limits when selecting Grok models in Cursor
Or at least a clear shared/usage-transfer mechanism between the two products after the acquisition

This would make the Heavy + Cursor combination feel truly unified rather than two separate products that only unlock each other.
Thanks!

Operating System (if it applies)

Windows 10/11
MacOS
Linux

Supporting the request, with one correction to the premise since it was written on Aug 20.

The “SuperGrok Heavy subscribers get free Cursor Ultra” part isn’t the current state anymore. On Aug 21 staff said that arrangement has ended - people who already claimed Ultra keep it, but anyone linking from now on gets Grok Bot access only. The docs now describe linking as a usage grant rather than something that puts you on a Cursor plan, so there’s no plan swap involved at all.

Which honestly makes this feature request more important, not less. If linking is only ever going to be a usage grant, then the useful version of that grant is exactly what you describe: let the Heavy pool actually be spent inside the editor, instead of it being a pool that works in Grok apps and Grok Bot but stops at the IDE boundary. Right now the link gives you the least useful half of what people were buying it for.

Mildly annoyed side note: the reason the first line of this request reads as out of date is that the change happened without a dated public announcement, so people were writing posts based on help copy that was still live. Worth flagging in case someone from the team reads this thread - clearer timing on these changes would save a lot of confusion.