Ravi

Grok Bot next session: keep its password and log back in tomorrow

Give the bot its own inbox, phone, and vault so a login wall is not a handoff.

Yesterday your Grok Bot signed up for a site and made up a password. Today it opens the same site, gets a login page, and the password isn’t in this chat. Ravi gives the bot its own vault, so the password stays with the bot and the next session can log in without you.

Why the next session gets stuck

Grok Bot works in its own browser on a cloud computer. Sites log you out, and a new chat may not have the password the bot typed last time. If the password only ever lived in an old chat, or with you, someone has to dig it out, paste it in, or reset it. That is the handoff this page removes.

Keep the password with the bot

The vault is an encrypted place to keep website passwords (domain, username, password) and key-value secrets such as API keys and tokens. Everything is encrypted at rest. It belongs to the bot, alongside its own inbox and phone number.

The rule is simple: when the bot creates a password, it saves it in its vault right away. When it hits that site’s login later, it reads the password back from the vault instead of asking you.

Logging back in tomorrow, step by step

  1. At signup, the bot creates a password and saves it in its vault with the site’s domain and its username, such as agent@raviagent.com.
  2. Tomorrow, in a new session, the bot opens the site and gets the login page.
  3. It looks up that site in its vault and reads the username and password.
  4. It enters them. If the site asks for a code, the code goes to the bot’s own inbox or phone; see Grok Bot returning 2FA.
  5. The bot is signed in and carries on. Nobody pasted a password.

The commands for saving and reading a password are on Credentials Across Worktrees. If the bot already lost one: The agent made a password yesterday and this chat does not have it.

Accounts that already exist

For an account you already use, change its email and phone to the bot’s in the site’s settings. Until then, codes still go to you. Once the account is the bot’s, have the bot set a new password and save it in its vault.

FAQ

Why doesn’t my Grok Bot remember the password from yesterday?

If the password was only typed into the site, the next session has nowhere to read it from. Saving it in the bot’s vault fixes that.

Where is the password stored?

In the bot’s vault: encrypted at rest, kept by Ravi, and tied to the bot. Not in a chat.

Does this work for a brand-new chat?

Yes. The vault belongs to the bot, not to one chat, so a new session that is still signed in to Ravi as the bot reads the same password.

What about authenticator apps?

The vault stores passwords and secrets. It does not generate authenticator-app codes. 2FA works by receiving the code a site sends by text or email; choose that method for the bot’s account when the site offers it.

Next Steps