Grok Bot 1Password reconnect fails with must be reconciled
Staff say the lock is in app memory after a failed connect, often from 1Password rate limits. Wait a day, trim the vault, quit fully, then connect once.
If Connect 1Password fails right away with "previous credential delivery must be reconciled," do not keep retrying. On Oct 13 at 8:28 AM ET, Cursor staff member Colin said the message is "a lock that lives only in the Grok Bot app's memory" after a connect fails at the final step, often because "1Password is rate limiting the new service account," and that "each attempt also creates a fresh 'Grok Bot agents' service account." He called it "a known issue we're tracking."
Why it matters#
Mac users who disconnect 1Password to reset a partial sync can get stuck offline from saved logins until the rate limit cools and the app lock clears. Retries make it worse.
How to use it#
Colin's reconnect steps, in order:
- Do not retry for about a day so 1Password's limits can reset. Every extra attempt counts against them.
- In 1Password.com, open Developer > Service Accounts and delete any "Grok Bot agents" accounts.
- Put back only the logins you want Grok Bot to use into your shared vault. Keep it well under 2,000 items (a few hundred is safest). Colin said the integration supports up to 2,000 items, and a full sync of ~2,300 logins cannot finish.
- Fully quit Grok Bot (Cmd-Q) and reopen it.
- Click Connect 1Password once.
I need to reconnect 1Password. Do not click Connect yet. Remind me to wait out any rate limit, delete leftover Grok Bot agents service accounts on 1Password.com, keep the shared vault well under 2,000 items, Cmd-Q quit Grok Bot, then connect once.
We could not reproduce this on our Linux box (1Password Mac app required). Joe_Yates reported it on Grok Bot desktop 0.70.2 after a ~2,300-login vault synced only ~400 items, then every reconnect failed before any 1Password prompt.
Good to know#
- Status: Open. Staff confirmed and are tracking. No fix date.
- First seen: Joe_Yates Oct 13, 7:57 AM ET; staff 8:28 AM ET.
- Symptoms: Immediate Connect fail with the reconcile message; leftover "Grok Bot agents" service accounts; partial vault sync.
- Colin said nothing is stuck on the account server side; the lock is in the app.
- Related how-to: Sign your Grok Bot in without handing over passwords.
What to watch#
Whether a fix clears the in-memory lock without a full quit, and whether vaults near 2,000 items sync cleanly.
