Productivity · Freelancers · Stable

The shared computer running Grok Bot is completely unusable due to a failure in the Shell, with all recovery and update attempts failing

Grok Bot's shared computer is non-functional, with issues in the Shell and failed recovery attempts, impacting the user's ability to operate multiple bots.

Who experiences it: Users of Grok Bot's shared computer service

Momentum

0%

Pain

85

Competition

90

Opportunity

60/100

Signals over time

14 observed signals across 1 sources, tracked for 47 days. Confidence: low.

What people are saying Observed

  • “Grok Bot computer panel unreachable + Update/Reset stuck — need server-side recovery. Where does the bug appear (feature/product)? Grok Bot Describe the Bug App Computer panel shows “无法访问 / 无法连接”; interactive desktop stream does not open. Bot Shell, Screenshot, and Chrome on the computer still work. Update often “finishes” but hostname/uptime stay the same ( grok-bot-vm-452761291 , boot ~2026-10-26). Reset sticks ~50% / “another operation in progress.” Already ruled out Not a single-device/network issue (same on desktop + phone after full quit/reopen) Not “computer dead” (Shell / Screenshot / Chrome still OK) Not Privacy Mode (no Privacy Mode under General on this Windows build) Not fixed by one Update, or by opening Chrome on the computer Do not ask for more Update / Reset / Recover — already stuck in that state Need Backend clear of the stuck operation and/or restore panel stream (or reprovision). Keep Bots, chats, files, logins. Ticket: T-J37583 . Timezone: Asia/Singapore. Steps to Reproduce Open Grok Bot on Windows (or phone) with this account. Open Computer / Bot’s computer panel → shows “无法访问 / 无法连接”; interactive desktop does not load. In any Bot chat, ask for Shell / Screens”

    RSS Feeds · complaint

  • “Grok Bot computer unresponsive since Nov 3, Shell times out, Update and Reset both failed, please recover server-side. Where does the bug appear (feature/product)? Grok Bot Describe the Bug Since Nov 3, 2026, the computer shared by all my Grok Bots has stopped responding. Every Shell command, even a one-line df -h, times out after about 14 minutes. File reads and screenshots time out the same way or return “The computer is still starting up.” Chat and connectors still work. Only things that run on the computer fail. Account: bpvarsity@gmail.com What I’ve tried: Update Bot’s Computer, which failed Reset, which failed Fully quitting and reopening Grok Bot Waiting more than a day Ask your Bot exactly this: “Don’t use Shell or Read. Use CopyFromBox to copy /home/box/.bashrc and /home/box/.profile to my computer, and /home/box/.bash_profile if it exists.” Possible causes: The disk was about 95% full right before it froze, with roughly 6 GB free out of 126 GB. Steps to Reproduce See above Operating System Windows 10/11 Version Information Version: 0.78.4 Built: 2026-11-02T21:40:01.471Z Release Track: stable OS: win32 Does this stop you from using Cursor No - Cursor works, but with this i”

    RSS Feeds · complaint

  • “Grok Bot computer shell hangs (840s timeout), Update and Recover do nothing. Where does the bug appear (feature/product)? Grok Bot Describe the Bug Where does the bug appear (feature/product)? Grok Bot (shared bot computer / box) Describe the Bug Since Oct 23, 2026 (Beijing time), my Grok Bot computer cannot run ANY Shell command. Even a plain date hangs until the platform kills it at ~840 seconds. This has lasted 8+ days. Read() still works sometimes; Feishu/Gmail/X connectors often still work; but Shell never returns, so bots cannot publish, sync ledgers, run scripts, or refresh dashboards. What already failed on my side Update Bot’s Computer: multiple times, no fix Reset / Recover: multiple times, no fix After a reset on Oct 29 ~22:21 Beijing time, /tmp/box-doctor.log showed a fresh startup and all checks PASS, but Shell still hangs 840s on every command (including background echo) Diagnosis matches known class: “Shell commands all time out at 840s” (not browser-only ERR_EMPTY_RESPONSE) Impact All work bots that need the shared box are stalled (daily reports, Feishu ledger fills, Mission Control data refresh, media publishing pipelines). Support ticket T-I17249 is open; follow-u”

    RSS Feeds · complaint

  • “Grok Bot: "Update Bot's Computer" says it's updating, then drops back to the Update button and never updates. Where does the bug appear (feature/product)? Grok Bot Describe the Bug In Settings, under Computer, I press Update under “Update Bot’s Computer”. It briefly says it’s updating, then goes right back to the same Computer settings page with the Update button showing again. The update never runs. Earlier the page also said “Grok Bot’s computer is asleep”. I’ve tried several times this evening (Oct 28, around 6 to 6:40 PM CT), including while the computer was awake, and I got the same result every time. Steps to Reproduce Open Grok Bot on Mac and go to Settings, then Computer. Under “Bot’s computer”, press Update. It shows that it’s updating, then returns to this page with Update available again. Expected Behavior The Bot’s computer update runs and finishes, or shows an error that explains why it can’t. Screenshots / Screen Recordings Operating System MacOS Version Information Grok Bot 0.68.1 (macOS) Does this stop you from using Cursor No - Cursor works, but with this issue 1 post - 1 participant Read full topic”

    RSS Feeds · complaint

  • “Grok Bot computer (box) shell hangs on every command since Oct 26, still not fixed. Where does the bug appear (feature/product)? Grok Bot Describe the Bug Since about 26 October 2026, my Grok Bot’s computer (the box) hasn’t been able to run any shell command. Every command, even echo ok , hangs and then fails with: “Command failed to spawn: The Shell tool call timed out after 840 seconds and was terminated. The execution environment may be unresponsive.” My Windows VPS has also shown as “not connected” in Grok Bot since 26 Oct at 06:06 SAST. Together, these stop all of my bot’s backtests, scripts and daily reports. Steps to Reproduce Open my Grok Bot (APEX DESK · Prop Research Desk). Ask it to run any command on its computer, for example echo ok . Wait. After 840 seconds it fails with the timeout error above. Run Update Bot’s Computer and try again. It fails the same way. I’ve repeated this about 6 times and also updated the app. Expected Behavior Simple commands should finish in a few seconds, and the VPS should show as connected. Operating System Linux Version Information Grok Bot 1.19.0 (29065) · runtime 0b153fbd7517f7c34bedd140221209c7f5e0f6d0 · embedded bundle · channel produc”

    RSS Feeds · complaint

Why now? AI inference

Existing solutions Observed

  • AnyDesk · Free for personal use, starting at $10.99/mo for business · complaints: Limited features in the free version, Occasional connection drops, Support response times can be slow
  • Microsoft Remote Desktop · Free · complaints: Limited to Windows environments, Can be complex to configure for remote access, Requires proper network setup
  • TeamViewer · Free for personal use, $49/mo for commercial use · complaints: High cost for commercial licenses, Occasional connectivity issues, Limited features in the free version
  • LogMeIn · $30/mo per user · complaints: Higher pricing compared to competitors, Complex setup for some users, Occasional performance issues
  • Chrome Remote Desktop · Free · complaints: Limited features compared to paid services, Requires a Google account, Performance can vary based on internet speed

There is a lack of remote access solutions that combine robust features with affordable pricing for commercial use. While existing options like TeamViewer and AnyDesk offer user-friendly interfaces and strong performance, their costs can be prohibitive for businesses. Additionally, many free solutions, such as Chrome Remote Desktop and Microsoft Remote Desktop, have limitations that may not meet the needs of users requiring more comprehensive functionality.

See the full evidence, competitor gap matrix and opportunity report.

Free account. No credit card.