Cursor CLI
Grok build (grok official command line interface) is buggy. Although I like it has /goal feature, I would rather use cursor-cli,
but now grok plans (supergrok, supergrok heavy) have a quite generous composer-2.5 quota.
I want to use my grok plan with cursor-cli.
Hey thanks for the feature request.
A small clarification on the tech side. composer-2.5 is Cursor’s own model. It is not part of Grok plans like SuperGrok or SuperGrok Heavy. So that generous quota for composer-2.5 in the Grok plan is probably a mix up.
On the request itself. Right now you can’t authorize cursor-cli with your consumer Grok/xAI subscription to have its quota pay for use in Cursor. Use in Cursor CLI goes through your Cursor plan. Grok/xAI is not a first-class BYOK provider yet so you won’t be able to connect the SuperGrok subscription specifically. I don’t have a timeline for this.
I left it as a feature request. If something changes I’ll reply in the thread.
composer-2.5 is available on grok bulid since jun 1. And when using composer 2.5 as the model the % usage increases very slow.
To clarify so we’re 100% on the same page: the Grok models themselves are already available in cursor-cli, and they’re covered by your Cursor plan. As I understand it, you want something else: you want your SuperGrok subscription quota to pay for usage in cursor-cli, instead of paying Cursor separately. That’s about subscription portability between two products, not about whether the model is available.
And thanks for the correction about composer-2.5, you’re right, I’ll correct my earlier reply. composer-2.5 can indeed be offered on the xAI side in Grok Build, which is a separate product with its own billing and quotas. But how that quota is charged is xAI’s rules, and it doesn’t carry over to Cursor.
On the main request: you can’t link a consumer Grok or xAI subscription to cursor-cli so that its quota pays for usage in Cursor right now. Grok or xAI isn’t a first-class BYOK provider yet. Usage in cursor-cli always goes through your Cursor plan.
I’ll leave this thread as a feature request. If anything changes in this direction, I’ll post an update here.