Bot: Grok Bot (agent id e0a8c89a-968b-44b4-b73f-cfa3215ee44e) User: Abdul Rauf Khan, timezone Asia/Karachi (PKT, UTC+5) When it started: Friday, Nov 6, 2026, around 10 PM PKT. It’s still happening as of Saturday, Nov 7, 8:01 AM PKT.
What happens
Chat replies still work normally.
Anything that needs the bot’s computer never finishes. That includes running a command, reading a file, and checking system status.
Even trivial actions hang. A one-line uptime check and reading the last 15 lines of /home/box/.bashrc both stalled.
Timeline (PKT)
Nov 6, about 10 PM: A simple text search command timed out after 840 seconds and was terminated, which is the first sign of the hang.
Nov 7, 3:17 AM: The user noticed a restart was taking very long. Reading the computer’s troubleshooting file hung for over 4 minutes.
Nov 7, 3:33 AM: The user said “Reset” and “Update Bot’s Computer” in Settings don’t work either and stay stuck.
Nov 7, 3:33 to 3:45 AM: A process listing hung for about 3 minutes, and an uptime check hung for about 9 minutes.
Nov 7, 7:57 AM: Reading two small files (/home/box/.bashrc and /home/box/.profile) hung for about 2 minutes.
What’s been tried
Updating and resetting the bot’s computer from Settings both get stuck and never finish.
Stopping all background work went through, and nothing was left running.
Killing processes from inside the bot wasn’t possible, because no command ever ran.
No outage or known issue was posted in the app.
Impact
None of the bot’s work that needs its computer can run, including files, commands, the browser and desktop tasks. The same computer is shared by all of this user’s bots, so they’re probably affected too.
Request
Please force-restart or reprovision the bot’s computer from your side, and check why both Reset and Update hang.
Steps to Reproduce
Steps to reproduce
Open the Grok Bot chat (agent id e0a8c89a-968b-44b4-b73f-cfa3215ee44e).
Ask the bot for anything that uses its computer, for example: “Use Read to show me the last 15 lines of /home/box/.bashrc” or “Run uptime.”
Expected: the result comes back within a few seconds.
Actual: nothing comes back. The bot waits from 2 minutes up to 14 minutes until the request is cancelled or times out.
Open Settings and click “Update Bot’s Computer” or “Reset.”
Expected: the computer restarts and works again.
Actual: it stays stuck and never finishes.
Reproduction rate: every attempt since about 10 PM PKT on Nov 6, 2026, on three different devices. Chat-only replies keep working the whole time.
Expected Behavior
Expected behaviour
Small commands like uptime and reading small files like /home/box/.bashrc finish in a few seconds.
Longer commands either finish or can be moved to run in the background, and they never freeze the bot.
If something does hang, the bot can stop it.
“Update Bot’s Computer” and “Reset” in Settings finish within a few minutes and bring the computer back working. If they fail, they should show a clear error rather than staying stuck.
If the computer is unavailable, the app should say so plainly instead of leaving requests hanging with no message.
You can’t force-restart or recreate the bot’s computer yourself. Only Cursor can do that on their side. But there are a few things worth trying while you wait.
Reopen the conversation or click retry from the error state.
Fully restart the Grok Bot app and check if there’s an app update in Settings > Updates > Check for Updates. The app and the computer update separately.
If you see the Recover Grok Bot’s Computer button in the UI, use that.
Only after that, try Update Bot’s Computer. Use Reset only as a last resort.
A couple of notes:
Don’t run Reset or Update repeatedly while a previous attempt is still stuck. It probably won’t make things faster.
Reset and Recover rebuild the computer from the latest saved data. If the computer is unavailable, the newest changes might not come back. If there’s anything important there, keep that in mind.
If you’re on an Enterprise team, your admin can recreate Recreate or stop Terminate your computer in Manage Member Computers and Data on the Grok Bot page in Security & Compliance. Terminate keeps the disk, and the next session starts on a fresh computer. More here: Manage Grok Bot computers | Cursor Docs
Also, there are a few similar threads in Suggested on the right with the same symptoms like 840s timeout and stuck Reset or Update. It may be worth following those for replies from the team.
Hi @Abdul_Rauf_Khan, the most likely cause is a line in one of the computer’s startup files (/home/box/.bashrc or /home/box/.profile), usually added by a bot setting something up to start automatically. It launches a background program that never lets the shell finish starting, so every command and file read hangs. Update and Reset don’t clear it because they bring back the same files.
You can swap those files for the clean defaults using the Grok Bot desktop app on your own computer (same account):
In a new chat, tell one bot “Don’t run any commands.”
Ask it to copy a small file from your computer to its computer and back. If that returns within a few seconds, continue. If it hangs, stop and reply here.
Ask the bot to CopyFromBox /etc/skel/.bashrc, then CopyToBox it to /home/box/.bashrc.
Do the same with /etc/skel/.profile to /home/box/.profile.
Wait a minute, then run Update Bot’s Computer once.
Ask a bot to run echo ok to confirm.
This also removes anything else your bots added to those two files. Please hold off on more Resets until then. To keep it from coming back, have your bots start background programs from a routine rather than a startup file.
@Colin thank you for your response. I tried the above. File copying works fine but I don’t see an option to Update Bot’s Computer. It says Your computer is on the latest version.
How can I avoid this going forward? I also intend to provide Grok Bots setup as a service to my clients, Insha Allah , so what’s the best way to avoid such hang ups?
I’m having the same issue: chat works, but commands and file reads hang across all my bots. My computer shows the latest version, with only Reset available. Could you restart the shared computer from your side while preserving my files?