Where does the bug appear (feature/product)?
Grok Bot
Describe the Bug
On October 8, 2026, my Grok Bot cloud computer’s files reverted twice to an earlier state, losing approximately two hours of video rendering and editing work. Neither I nor my bots initiated Reset, Recover, or Update.
Existing email support ticket: T-G83821. The email thread contains timestamps and diagnostic evidence. All support replies so far have been signed by Sam, Grok Bot’s AI Support Assistant. After I requested human review, Sam stated that it cannot inspect backend/infrastructure logs or transfer the case to an engineer.
@mohitjain @kevinn Could a staff member please help route this ticket to a human support owner and the relevant engineering team?
Steps to Reproduce
This was an unexpected incident; I do not have a reliable way to reproduce it on demand.
- Use the Grok Bot cloud computer for video rendering and editing, saving work in /workspace.
- On October 8, observe that recent files/edits have reverted to an earlier state without any user- or bot-initiated Reset, Recover, or Update.
- The rollback occurred twice that day, once before approximately 14:00 and once around 15:00 China time (UTC+8). Both times the file state appeared to return to around 13:00–13:15.
Detailed observations and timestamps are already in the private email ticket for engineering review.
Expected Behavior
Saved files should persist during normal use. Please investigate why recent changes disappeared, preserve relevant logs and available snapshots, and assess whether the lost files can be recovered. Please confirm any safe next steps before asking me to perform operations that could overwrite recoverable data.
Operating System
MacOS
Version Information
Grok Bot desktop app on macOS; exact version not yet collected. I can provide version information in the existing support thread if needed.
Additional Information
Please associate this report with email ticket T-G83821 and continue account-specific investigation through that existing email thread.
Requested follow-up:
- Confirmation that a human support owner has accepted the ticket and that engineering review is arranged.
- Preservation of relevant logs and available snapshots, and a recovery assessment.
- A log-based explanation of the rollback and measures to prevent recurrence.
- An expected time for the next update.
The underlying cause has not been independently confirmed by an engineer. Account email, cloud computer/store identifiers, conversation IDs, and private diagnostics are kept in the email ticket and omitted from this public post.
Thank you.
Does this stop you from using Cursor
Sometimes - I can sometimes use Cursor