METAGROK
GROK BOT / when-one-bot-loses-computer-use

When one Bot loses computer use after a handler restart

when-one-bot-loses-computer-use

Use this when one Bot on your roster can still use shell and files, but screen and browser actions fail with No computer-use handler is registered on this exec daemon. This is a known issue. Staff gave interim steps. There is no published fix. Checked Oct 16, 2026.

Cursor staff (Colin) said on forum thread 174931 on Oct 16, 2026 that they are already tracking this. During the Bot computer disruption on the afternoon of Oct 14, the part of the computer that handles screen and browser actions for that Bot restarted while the computer was overloaded, and it came back without screen control. Each Bot has its own handler. It stays in that state until it restarts. Nothing in your settings or plan will change it.

The original report said only one of four Bots was affected. That matches staff's “each Bot has its own” wording. Docs and the Bot changelog do not describe this error. Do not treat a missing docs entry as proof your plan is wrong.

Keep the work moving

Staff's interim steps:

  1. Keep using that Bot for shell and files. Staff said those still work.
  2. Hand screen and browser steps to one of your other Bots for now. Your other Bots are not automatically in the same state.
  3. Open Settings and look at the Bot's computer. If Settings shows an update available, running Update should bring screen control back.
  4. If Settings says you are already on the latest version, Update will not change anything yet. Do not loop Update hoping it will.

Update is not a guaranteed restore. Staff tied it to an update being available. If none is offered, wait for a restart or a staff fix. Do not Reset the Agent Computer for this error unless staff later ask for that. Reset is a different, last-resort path on Update or recover the Grok Bot computer.

What this is not

This is not a plan or settings misconfiguration. Staff said those will not change the handler state. It is also not “every Bot on the account lost computer use.” One Bot can sit without screen control while the others still click and browse. Files, browser sessions, and logins on the shared computer stay shared; only that Bot's screen-control handler is stuck.

There is no published timeline. If you reply on the thread, say which Bot lost screen control, whether Settings offers an update, and whether shell and files still work.

Related

Pitfalls

  • Pressing Update when Settings already says you are on the latest version. Staff said that will not change anything yet.
  • Resetting the shared computer because one Bot lost screen control. Staff's interim is shell, files, and another Bot.
  • Changing plan or local-execution settings to “fix” the handler. Staff said those will not change this state.