Where does the bug appear (feature/product)?
Grok Bot
Describe the Bug
Existing bots on my shared Bot computer cannot start a desktop/browser. Screenshot and computerUse fail with: All screens on the shared computer are in use. Try again in a moment.
This is not a single-bot issue: at least two older bots fail the same way. Shell and chat work; in-box box-doctor reports all PASS. Clearing local sand-window lock files under /tmp does not help. Settings → Computer → Update Bot’s Computer shows the computer is already the latest version — there is no Update button. I have not pressed Reset.
Diagnostic: I created a new bot. At 2026-11-06 ~12:58 Asia/Hong_Kong that new bot’s Screenshot succeeded (empty desktop UI; no “All screens in use”). So host capacity is not exhausted; older bots’ screen leases appear stuck. Box uptime was still multi-hour (instance not rematerialized by Update). Browser-dependent daily work was blocked until done manually.
Steps to Reproduce
-
On an older existing bot, ask for a Screenshot or any browser/desktop step.
-
Observe:
All screens on the shared computer are in use. Try again in a moment. -
Ask a second older bot — same error.
-
Open Settings → Computer → Update Bot’s Computer — UI says already latest; no Update action.
-
Create a brand-new bot; ask it to Screenshot — succeeds (~12:58 HKT on 2026-11-06).
Expected Behavior
Existing bots get a working desktop/browser again. Please refresh this account’s Bot computer from the latest backup without Reset, clearing stuck screen leases (as discussed in related forum threads). Keep all bots, files, and logins.
Operating System
Windows 10/11
Version Information
Windows and iOS: Grok Bot 0.79.2
Timezone: Asia/Hong_Kong
Additional Information
-
Timezone: Asia/Hong_Kong (UTC+8)
-
Observed: 2026-11-06 ~11:40–13:00 HKT
-
box-doctor: all checks PASS
-
Related public threads: forum.cursor.com , forum.cursor.com
-
Please do not ask me to Reset.
Does this stop you from using Cursor
Sometimes - I can sometimes use Cursor