Grok Bot: browser proxy 8791 down + all 10 screen locks stale (ticket T-I55701)

Where does the bug appear (feature/product)?

Grok Bot

Describe the Bug

My Grok Bots cannot use the desktop or browser. This has continued for about a week.

  1. Browser egress proxy on 127.0.0.1:8791 is not running (no sand-egress-tunnel / supervise-egress-tunnel). curl via that proxy returns exit 7 / HTTP 000. Direct shell network works (box-doctor egress PASS).
  2. box-doctor reports FAIL novnc-forks: no fork noVNC websockify on 6081.
  3. All 10 slots under /tmp/sand-window-locks.d have stale .bound files pointing at dead PIDs (slots 2-11). Desktop/browser attempts fail with “All screens on the shared computer are in use” / browser not ready.
  4. “Update Bot’s Computer” around 2026-11-04 17:00 JST did not move the box to a fresh instance. An Update on 2026-10-29 also failed. I have not run Reset, per Support’s earlier guidance.

Shell and non-browser work still function. Without the browser I cannot do my normal work.

Support ticket: T-I55701. Follow-ups 2026-11-02 and 2026-11-04 17:05 JST. No reply yet.
Related forum threads: 177180 and 176333 (same symptoms; staff said known issue).

Steps to Reproduce

  1. Ask any bot to open a website or take a screenshot.
  2. Bot reports screens in use / browser not ready, or the desktop view stays on “Waking Up…”.
  3. On the box: no process on 8791; curl -x http://127.0.0.1:8791 https://example.com fails; all 10 .bound lock files point at dead PIDs.
  4. Run Update Bot’s Computer — problem remains.

Expected Behavior

Each bot gets a working desktop and browser. Proxy 8791 should be up, and screen slots should not stay bound to dead processes.

Operating System

Windows 10/11

Version Information

Grok Bot 0.78.4 (Windows)

Does this stop you from using Cursor

Yes - Cursor is unusable

Hey @Oekaki, update from our side. I’ve refreshed your bot’s computer onto a clean, fully up-to-date instance (your files and bots are intact). That should bring the browser proxy back. Please fully quit Grok Bot and reopen it, then ask one bot to take a screenshot and open a site. If you still see “All screens … in use” after that fresh relaunch, reply here and I’ll keep digging - that part points to a separate issue we’re already tracking.