Engineering
Blocking the Gmail plugin does not close an open browser session
You blocked the connector and still watched the agent touch email.
What hurt
Rexei (@iamrexei) warns: if email is already open in the browser, blocking the Gmail plugin will not close it. Four external tools he lists for clearer boundaries (Steel Browser, Sandbox Runtime, Cerbos, Daytona) are for your own stack — not toggles inside Grok Bot. Separate the browser session and stop Send before you split roles. Not affiliated with xAI.
What to install or create
Tip + checklist. Close browser email sessions, fence Send, then assign roles. Do not invent Grok settings that do not exist.
Bots
Mail-aware bot
No Send without you. Separate browser session when possible.
Plugins
Gmail
Optional
Browser
Optional
Routines
None on the first run. Watch one manual pass first.
The prompt
This is a tip, not a pasteable system prompt. The author did not publish one. Follow the first-run steps.
First run
- 1Read https://x.com/iamrexei/status/2109727118049304971 (credit @iamrexei).
- 2Close any personal Gmail tabs the bot computer already has open.
- 3Turn off or limit the Gmail plugin if you want connector-level block — then re-check the browser.
- 4Fence Send/reply as Ask-first before multi-bot email roles.
- 5Optional: use a separate managed browser session for agents (his Steel note) — only if you run that stack.
Approval fence
Do not send email. Close or isolate sessions before granting access.
What to tweak
Steal the order: separate browser → stop Send → then roles. Plugin off ≠ session closed.
Source
Rexei @iamrexei · Original post
Not affiliated with xAI. We did not write this prompt. Third-party template terms still apply.
Pro pack
Want the full setup, not just the idea?
Pro packs give you the job text, prompts, schedules and pitfalls for popular use-cases.