Grok Bot Vault logins won't fill in the box browser (driver_unavailable)

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Grok Bot

Describe the Bug

Saved Vault logins can’t be filled into the Grok Bot box browser. On 11/5/2026 around 8:55 AM ET, secure fill returned driver_unavailable for both username and password on a saved login, and listing available secure values said no https page was open, even though the login page was loaded. It happened again at 9:03 AM ET on this forum’s own login page. The credentials are saved correctly. The only workaround is a manual screen handoff for every sign-in. This blocks every bot task that needs a saved login, so we can’t do our work. Please treat it as high priority. Also reported through in-app feedback.

Steps to Reproduce

  1. Bot opens a login page in the box browser.
  2. Bot calls secure fill with Vault refs for username and password.
  3. Secure fill returns driver_unavailable.

Expected Behavior

Username and password fields should be filled from the saved Vault login.

Operating System

Linux

Version Information

Version: unknown
OS: Linux (cloud box)

Does this stop you from using Cursor

Yes - Cursor is unusable

10

Hi @Globe_Teck, your saved logins are fine. The fill is failing because the bot isn’t receiving a response from its browser driver when it tries to fill. That’s also why it said no HTTPS page was open, even though the login page was loaded.

I’ve passed this to the team along with the times of your attempts this morning. Other users are seeing the same thing.

For now, the screen handoff is the reliable way to sign in.