Stop pasting passwords into your AI. There's a cleaner way now. Every bot that d
By Jaspinall · November 10, 2026 · Curated by George's Blog
Stop pasting passwords into your AI.
There's a cleaner way now.
Every bot that does real work hits a login screen sooner or later. The supplier portal. The shipping dashboard. The ad account.
The old move was dropping the password in chat and hoping for the best. Then it sits in a chat log forever, next to everything else you typed that week.
Grok Bot gives you two better options, and I use both.
The Vault lives in Settings. You save logins, cards and contact info once, and your bots fill them in when they need to sign in or check out.
1Password connects without a shared vault. When a bot needs a login, you approve it in the 1Password app, and 1Password fills it into the bot's browser. The bot never sees the password.
Here's the setup I'd copy this week.
1. Pick the three logins your bots hit every week. Not all of them. Start with the boring portals that eat your mornings.
2. Save each one in the Vault and fill in the Hints field. Hints tell bots when to use each entry. "Use for reorders only, never the main store admin" is a good hint.
3. Keep the sensitive stuff in 1Password. Bank, payroll, the main store admin. Those get approved one login at a time.
Bots try your saved Vault logins and cards before a password manager. So the Vault is your everyday lane, and 1Password is the locked door.
Money still waits for you. The Vault's Payments tab sets which card bots use first. It doesn't skip your approval on a purchase.
On a team plan, managers can add logins to a Team Bot's own Vault, and the bot signs in with them for the whole team. No more shared passwords floating around in Slack.
The image below is example data, not my real Vault.
One rule keeps this clean. If you wouldn't hand a new hire the password on day one, don't hand it to the bot either. Give it an approval step instead.
🪿