How this helps you
Knowing that every Bot can use every login helps you decide which accounts to connect and which actions should always ask first.
✦ Try it
Save this as a skill called safety-baseline and follow it in every task: never ask me to paste a password or code into chat; use Vault, 1Password or a Secure Form. Use the smallest account that can do the job. Never run commands on my own computer. If a routine's source changes, pause the routine and tell me. Ask me first before deploys, emails, payments and accepting legal terms.
What they did
@0xfelliu summarised a security baseline from the enterprise docs: no passwords in chat, use task-sized accounts, pause the routine if its source changes, and ask first for payments and emails. His post also says never allow local execution on your laptop and keep auto-approve narrow.
Who it's for: Everyone, before connecting real accounts.
How to try it
- Never paste a password into chat. Use the vault or a password manager.
- Sign in with accounts sized to the task, not your main admin account.
- Do not allow local execution on your laptop.
- If a routine's source changes, pause the routine.
- Require a yes for deploys, emails, payments and legal terms, and keep auto-approve narrow.
What to expect
A saved skill your Bots follow, so the same five rules apply in every chat.
Common mistakes
- Assuming one Bot's login is private to it. All Bots share one computer, so every Bot can use it.
- Using separate Bots as a security boundary. The official docs say not to.
- Signing in with your main admin account when a smaller one would do.
Related tips
- Vault: logins, cards and contact info: Your Bot never sees saved passwords or card numbers. One catch with saved cards.
- Use your 1Password with Grok Bot: Connect 1Password, approve each login in the 1Password app, and it fills the sign-in without the Bot seeing the password.
- What actually stops a coding Bot (and what is only advice): Of 15 operations tested, only a merge to main hit a hard stop. Skill-file rules are only advice.
- Connect your apps from chat, or through one MCP hub: Ask a Bot to connect Gmail and other accounts in chat, or use one Composio or Zapier account if you have many tools.
- Dad Bot: get your parents started: A patient helper that walks older folks through it one step at a time.
- Research to purchase, with your approval: It researched pet insurance, compared quotes and paid with Link only after the user said buy.
- Build a Tesla Bot with Tesla's Fleet API: A Bot that checks your Tesla, runs climate and charging, and asks before it unlocks anything, set up through Tesla's free developer Fleet API.
- Roll out Grok Bot to a team with admin guardrails: From the official admin video: set team rules, auto-review, plugin and network allow lists, then start with a pilot group before inviting everyone.
- Set up Auto-review rules: ask first for anything you can't undo: Turn on Auto-review, then add Ask first rules for money, publishing and sending. When rules clash, Ask first wins.
- Test your Bot against instructions hidden in email: Send your Bot's inbox two booby-trapped emails, check it ignores them, then add a house rule and a sender filter.
Worth knowingAll your Bots share one cloud computer, so browser logins, files and command-line credentials are shared between them. The official approvals page also suggests setting Settings, Computer, Your computer to Never allow unless a Bot needs your local files.Next in Security & Vault →Test your Bot against instructions hidden in email
Learn more: How to Use Grok Bot: A Beginner's Guide (2026) · All Grok Bot security & vault tips