Title: Grok Bot computer won't reset or update, and browser tools are blocked

Where does the bug appear (feature/product)?

Grok Bot

Describe the Bug

Body: Since Nov 16, my Grok Bot’s cloud computer won’t reset. I clicked Reset on Nov 16 at night and tried Update Bot’s Computer on Nov 18 around 2:30 PM ET. Neither took effect. The computer’s boot time still shows Nov 16 at 7:02 AM, and all the old processes are still running.
Browser and desktop tools also fail every time with this message: “The box could not confirm that no saved credential is being filled into its browser, so this tool did not run.” Chrome is running on the box, but no screenshot or browser action works.
Chat and shell commands still work fine. Disk use is 74% with 34 GB free, so it doesn’t look like a space problem. I’ve backed up everything and paused all jobs. I emailed [email protected] and sent in-app feedback, but haven’t heard back yet.
Has anyone seen this, or found a way to force a reset?

Steps to Reproduce

Here’s a steps-to-reproduce section you can add to the post:
Steps to reproduce:
Open a Grok Bot whose cloud computer has been running for a few days with several bots and background jobs on it.
Open Settings and click Reset Bot’s Computer. In my case that was Nov 16 at night.
Wait, then check the computer’s boot time with uptime -s in a shell. It still shows the old boot time, and the old processes are still running.
Try Update Bot’s Computer. I tried on Nov 18 around 2:30 PM ET. Same result: no restart.
Ask the bot to take a screenshot or do anything in the browser. It fails with “The box could not confirm that no saved credential is being filled into its browser, so this tool did not run.”

Expected Behavior

Expected: The computer restarts fresh, and the browser tools work. Actual: No restart happens, and every browser or desktop action is blocked. Chat and shell still work.
I can’t tell whether it happens on every account or only on a busy, long-running computer like this one, so I’d leave that unstated.

Operating System

Linux
iOS
Other

Version Information

Grok Bot 1.26.0 (29388) · runtime d669c5c5da0f7cb9cf4136900f15dd8573415f75 · update 22e6a372-e40d-4acb-a6c9-5724a8a10180 · channel production

Does this stop you from using Cursor

No - Cursor works, but with this issue

Hi @Kevin_Hu1, your bots are on a new computer with a larger disk, with your saved files restored in full. The browser and desktop tools should work again.

The larger disk is temporary. Your storage needs about 135 GiB to restore and a standard computer fits about 120 GiB, so please clean it up to get below that, with room to spare. Asking a bot to list the largest folders in /workspace is the quickest way to see what to remove.

I’m having a similar issue, here’s the error report from my bot:

Title: Scheduled routine runs no longer get a browser (computerUse) subagent

Bot: agent id 40153a0f-e104-4c34-a08e-2b66cf110f73

What happens:
Scheduled runs start without any browser/computerUse subagent available, so they cannot open a website. The run itself completes (calendar connector reads and file writes on the bot’s computer still work) and reports “no browser subagent available.”

Same bot, same browser, run from the in-app chat: browser subagents work normally. Manual runs on Nov 18 at 3:35 PM ET and 9:13 PM ET browsed and completed fine.

Timeline (ET, UTC-5):

  • Nov 16 3:13 PM through Nov 17 9:19 AM: scheduled runs browsed normally (6 runs).
  • Nov 17 12:04 PM: scheduled run browsed normally.
  • Nov 17 9:13 PM (02:13 UTC Nov 18): first scheduled run with no browser.
  • Nov 18 12:13 AM (05:13 UTC): browsed normally again.
  • Nov 18 ~3:14 AM (08:14 UTC) to now: every scheduled run has had no browser. That’s 11+ website runs and 2 checkout runs in a row, most recently Nov 19 at 6:05 AM ET.

What did not change:

  • The routine prompts were not edited to remove browser use. The only edits were report and wording rules, made after the breakage began.
  • The user’s computer being offline is not the cause. Runs that worked on Nov 17 morning were also using the bot’s own network.

Expected: scheduled routine runs can dispatch a browser/computerUse subagent, as they did through Nov 18 12:13 AM ET.

Was the browser removed from scheduled/automation runs on purpose, or is this a regression? Is there a setting to turn it back on?

Thanks for any help

Please create a new thread.