When you enter API keys with the secure in-chat card, they land in the computer’s secret store. Later — after sleep, a connection drop, or quitting/reopening the Grok Bot app — that store gets emptied. We then can’t create service requests in MIPP until you re-enter both keys. Happened ~6 times today alone. Cursor staff already confirmed this on another user’s report: reconnect sync overwrites in-chat secrets.
Steps to Reproduce
Enter secrets via Grok Bot secure secret-request (in-chat card), not pasted in chat.
Confirm they exist in the box secrets store.
Let the desktop app reconnect (PC sleep, connection drop, or quit/reopen Grok Bot).
Check the secrets store again.
Expected Behavior
Secrets entered via secure secret-request should stay until I remove them. A reconnect should not wipe/overwrite the store.
Hey, thanks for the detailed report. You described everything correctly, and it’s the same issue that was confirmed in the neighboring thread. When the Grok Bot desktop app reconnects to your computer after sleep, a connection drop, or quit and reopen, it re-syncs its secrets list to the machine, and that sync currently overwrites what was saved via the secure in-chat card.
Important: this isn’t anything in your setup, and Update, Reset, or reinstalling won’t help. Your desktop app is already on the latest stable. This is an issue we’re tracking. I can’t share an exact ETA yet, but I’ll post in this thread when there’s an update.
As a temporary workaround so the MIPP workflow doesn’t break after every reconnect, you can ask the bot to store both keys in a file inside its own agent folder on the Grok Bot computer. That folder isn’t affected by the sync. Keep in mind this is less secure than the secure card, so once the issue is fixed, it’s best to move the values back into the secure card.