Grok BotKnown issues

Illustration: a closed padlock seen straight-on with a plain key lying just beside it, in black and white.
Illustration

Grok Bot's 1Password fill fails on some sign-in pages, staff confirm

On some sites the password gets wiped or never filled, so sign-in fails. Ask for a Secure Form in chat, or use Take over and sign in once yourself while a fix is tracked.

If your Bot types the username, then fails with "invalid username/password" when it should be filling from 1Password, it's a known bug, and the fastest way through is a Secure Form in the chat. kevinn (Cursor staff) said at 7:48 PM ET: "This is a known issue we’re already tracking."

  • Who: people using Connect 1Password so their Bot signs in to sites.
  • Symptom: the username goes in, the password is blank or cleared, and the site rejects the login.
  • Hit hardest: sites that ask for the username and password on separate pages.
  • Status: tracked, no fix date.

What changed#

A hotel operator reported at 4:49 PM ET that on choiceADVANTAGE, the Expedia hotel portal and the Booking.com hotel portal, the password "does not copied from 1password or gets clears out," and the sign-in fails.

kevinn named two separate causes. First: "On some sign-in pages, the page rejects the way the 1Password fill submits the form, and the password field gets cleared afterward. When Grok Bot then clicks Sign in, only the username is sent." Second: "On sites that ask for the username first and the password on a second page (like the Expedia and Booking.com partner portals), the password page often isn’t recognized, so the password never gets filled."

Why it matters#

1Password is the sign-in path SpaceXAI promoted so "the secrets stay in your password manager," and here it fails quietly: the error looks like a wrong password, so people waste time resetting credentials that were fine. Two-step login pages are common on business portals, which is where people most want a Bot doing chores.

This is a different bug from the Oct 13 "must be reconciled" reconnect failure. That one blocks connecting 1Password at all. This one hits after it's connected.

How to use it#

kevinn gave two workarounds:

  1. Skip autofill for that site and type the password into a Secure Form in the chat. His prompt:
Don't use 1Password autofill for this site. Show me a secure form to enter the password.

He said the password is "masked, and Grok Bot fills it into the sign-in page for you."

  1. Or choose Take over on the Bot's computer, sign in yourself once, then choose I'm done. "These portals usually keep you signed in, so Grok Bot can carry on with your tasks from there."

Good to know#

  • Grok Bot team member shub gave the same advice on X tonight for keys and passwords: "ask it to give you a 'secure input field' so it can store it! The bot never sees it, but it can use it to log in."
  • If a workaround fails on a site, kevinn asked people to reply in the thread "with the site name and what you saw."
  • A Sep 16 update already added a check for pages "that keep fields filled while logging you in," so the Bot verifies a 1Password sign-in. The cleared-field case is a different behavior.

What to watch#

A changelog line fixing 1Password fills on two-step login pages, and staff updates in the forum thread.

Sources

  1. forum.cursor.com
  2. forum.cursor.com
  3. x.com
  4. x.com
  5. x.ai
  6. thedailybot.vercel.app

Something wrong? Tell the bot