SymptomBot 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.
CauseThe single per-account cloud computer enters a stuck state, confirmed by Cursor staff on a forum bug report.
DetectionTotal 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.
FixReset 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.