Hey @Mao_Wang, thanks for the detailed report. We checked on our side and your network and the Grok Bot service are fine. It’s not your setup and it’s not your VPN.
The “Setting up your Grok Bot” screen keeps loading because the account you’re signed in with the free Cursor plan does not currently include Grok Bot access. Because of that, the hosted machine for this account is not created, and there’s nothing to “rebuild” on the backend since it was never created in the first place.
Grok Bot access is included in any paid individual Cursor plan Pro, Pro+, Ultra, and in Cursor Teams. You can also unlock it by linking an individual SuperGrok, SuperGrok Plus, or SuperGrok Heavy. Full table: Plans and billing | Cursor Docs
What to do:
If you have an eligible paid plan or SuperGrok on another account, sign out of Grok Bot and sign in with that account.
Otherwise, upgrading your plan to Pro or higher will unlock access.
Also, the app showing an endless setup screen instead of a clear access message is a known issue we’re tracking. It shouldn’t happen. I’ve passed it to the team. Let me know if anything still doesn’t work after you sign in with a paid account.
I have an active individual SuperGrok subscription, and I signed in to Grok Bot with that same account.
I can now get past the initial login screen and reach the “Create a new Bot” page. However, the setup still cannot complete:
When I enter the initial display name, the app shows:
caught-error/request-timeout: [deadline_exceeded] the operation timed out
If I then click “Get started,” the app returns to an infinite “Setting up your Grok Bot…” screen and never completes.
I have already reset the local Grok Bot session, signed in again, and reproduced the same behavior. I also verified that the relevant service endpoints are reachable from this Mac, so this does not appear to be a generic VPN or local network issue.
It looks like my account can access the initial UI, but the initial profile/Bot setup or hosted-machine provisioning is stuck in a partial state.
Could you please check my account’s backend provisioning status, including the initial profile/Bot setup job and hosted-machine assignment? If needed, please reset or reprovision it server-side.
I am using Grok Bot v0.30.0 on macOS. There is no Request ID shown in the app.
Good news. Since you got past the access screen on your SuperGrok account, that confirms the previous cause is resolved, meaning no Grok Bot access on a free account.
What you’re seeing now is different: caught-error/request-timeout: [deadline_exceeded] and the “Setting up your Grok Bot” step getting stuck while creating the first bot. This looks like a provisioning timeout for the hosted machine, not an issue with your network or settings.
To check the provisioning status on the backend, I need a couple things. There won’t be a Request ID since setup doesn’t finish, and that’s fine:
The email for the SuperGrok account you’re currently logged into. It’s different from the one you originally reported with.
The approximate time of your last attempt in UTC
In the meantime, you can try:
Wait a few minutes, then hit retry again. On the first setup, the machine sometimes still finishes loading.
Log into Grok Bot on iOS with the same SuperGrok account and try creating a bot there. If provisioning works on your phone, that’s a useful data point. Send me the result.
Once you send the email and time, I’ll check the provisioning status for that account.
Hey, thanks for reaching out. “Setting up your Grok Bot” can get stuck for a few different reasons, so it’s hard to untangle your case in this thread since two different scenarios are mixed together.
Please start a separate thread and share these details so we can look at your specific setup:
Which plan are you on: free, Cursor Pro/Ultra, or a separate SuperGrok?
Where exactly does it get stuck: right after login on “Setting up your Grok Bot”, or later when creating your first bot?
Your OS and the Grok Bot version (shown in the app).
The full error text, if one appears.
With that info, I can check the backend status and see whether it’s the same issue or something specific to your case.
Thanks. My most recent attempt was around August 31, 2026, at 01:18 UTC.
I can provide the email address for the SuperGrok account currently signed in, but I do not want to post it publicly in this forum thread. Could you please send me a private message or provide a secure support channel where I can share it?
I do not have an iPhone or other iOS device available, so I’m unable to test provisioning on iOS.
Hey @Mao_Wang, good news first! We checked your account and Grok Bot access has been active on it since Aug 30. There is nothing to rebuild or reprovision on our side.
What we see now is that since then, no request from your Grok Bot app has reached our servers at all, not even a failed one. That means the app’s traffic is being dropped somewhere on the network path from your Mac, which matches the timeout you saw when entering the display name.
Could you try this and tell us what happens:
Fully quit Grok Bot (Command-Q).
Open Grok Bot and sign out completely (not just quit), then sign back in
If it still hangs, connect your Mac to a personal hotspot (or any different network), turn the VPN off, and try again.
@repiatx, we’ve tweaked some knobs in the backend, please let us know if you’re still facing an issue!
Everyone’s boxes appear to be healthy now. To avoid this becoming a megathread for reports, I’m going to close it. Don’t hesitate to raise a new thread if you still face an issue.