Grok Bot
All bots hung since Nov 5th. I’ve updated the computer, updated grok bot for Mac Desktop and conducted a full local recovery of files saved. My disk space is below 80% and grok bot is reporting the last local commits able to be recovered are on October 25th. I’m trying to recover between October 25th and November 5th.
Hi there!
We detected that this may be a bug report, so we’ve moved your post to the Bug Reports category.
To help us investigate and fix this faster, could you edit your original post to include the details from the template below?
Where does the bug appear (feature/product)?
Describe the Bug
A clear and concise description of what the bug is.
Steps to Reproduce
How can you reproduce this bug? We have a much better chance at fixing issues if we can reproduce them!
Expected Behavior
What is meant to happen here that isn’t working correctly?
Screenshots / Screen Recordings
If applicable, attach images or videos (.jpg, .png, .gif, .mp4, .mov)
Operating System
Version Information
agent about in your terminalIDE:
Version: 2.xx.x
VSCode Version: 1.105.1
Commit: ......
CLI:
CLI Version 2026.01.17-d239e66
For AI issues: which model did you use?
Model name (e.g., Sonnet 4, Tab…)
For AI issues: add Request ID with privacy disabled
Request ID: f9a7046a-279b-47e5-ab48-6e8dc12daba1
For Background Agent issues, also post the ID: bc-…
Additional Information
Add any other context about the problem here.
Does this stop you from using Cursor?
The more details you provide, the easier it is for us to reproduce and fix the issue. Thanks!
@Colin Wondering if you can help me fix this. The Grok Bot app on desktop is updated to current and I am on the most recent OS for Mac Studio. **
Title:** Inaccessible agent workspace: need to preserve files before reset
Where does the bug appear?
Agent workspace access and recovery. Please help confirm whether Cursor manages the affected environment.
Describe the bug
An agent’s existing working environment has become inaccessible. It may contain project files, uncommitted changes, unpushed local Git commits, test artifacts and run records that have not been copied elsewhere.
Our workflow was to commit work locally without necessarily pushing it to GitHub. We have recovered some files and histories to my Mac Studio, but several original November 5 work packages remain unaccounted for outside the inaccessible environment. Summaries of the work are not a substitute for the original files.
I need to restore access or preserve the workspace before considering a reset. I don’t know what a reset would retain, and I don’t want to lose recoverable data during troubleshooting.
Steps to reproduce
I don’t yet have a minimal reproduction. The issue affects an existing workspace containing prior work. The agent currently cannot access its original working files or run the commands needed to export them.
Expected behavior
Restore access to the existing workspace, or provide a non-destructive snapshot or export before any reset. I need to preserve:
Please explain what a restart, reset or environment recreation would retain or delete, and whether a disk snapshot or read-only recovery mount is available.
Operating system
Client: macOS on a Mac Studio. Exact macOS version and the affected remote environment’s OS are not yet confirmed.
Cursor version / model / request or background-agent ID
Not yet confirmed. I can provide the workspace identifier and any required diagnostics privately to support.
Additional information
This is a request to recover or preserve the environment. I have not authorized a reset. Please confirm whether Cursor manages this workspace, whether its disk and Git objects still exist, and what options are available to snapshot or export them before troubleshooting.
Hi @JM3710, your bot’s computer should be back up. It was moved to a new computer with a larger disk this afternoon. This is a temporary measure to get you back online, but it’s important you reduce the disk space used on the computer! The team is working on making this less of a footgun.