{"found":true,"collection":"failure_modes","library_url":"https://www.grokbotdb.com/library/fm.stuck-shared-computer","generated":"2026-09-06T05:32:11Z","citation":["Quote the record id and its source_url (or provenance if there is no URL).","Include last_verified or observed_at when present. Do not present an old date as current.","If tier is community and confidence is low, say so. Do not launder it into a fact.","If the database does not hold the answer, say that. Do not invent Grok Bot product claims.","Contradictions are data: when conflicts_with is present, report both records rather than picking a favourite.","Deprecated and removed records stay visible. They are history, not current guidance."],"record":{"id":"fm.stuck-shared-computer","title":"The shared cloud computer enters a stuck state and takes every Bot on the account down","symptom":"Bot failed to respond errors, fully black windows, and complete account lockout affecting all Bots at once. One user reported a lockout persisting from 21 to 23 August.","cause":"The single per-account cloud computer enters a stuck state, confirmed by Cursor staff on a forum bug report.","detection":"Total and obvious, but not attributable to any one Bot, which is what makes the shared-machine design the diagnosis. Reported as persisting through restarts, app updates and duplicated Bots.","fix":"Reset the Bot's computer, accepting that unsynced work can be lost. On the desktop app, fully quit and reopen before anything else, then update the app and reopen Agent Computer. Treat installed packages and temporary directories as disposable and keep durable state in files.","severity":"high","source_id":"src.tp.cellcog.problems","source_url":"https://cellcog.ai/blog/grok-bot-problems/","confidence":"medium","first_seen":"2026-09-03","last_verified":"2026-09-03"}}