Engineering
Custom rules: ✓ allow automatically vs ? ask first — and five doc gotchas
Full access with zero custom rules is the default security hole.
What hurt
@irongiantXBT read the security docs and wrote copyable custom rules. Settings are only ✓ allow automatically and ? ask first. Setup: Settings → Custom rules → pick action → ✓ or ?. Doc notes: ? always blocks and wins clashes; ✓ does not override the reviewer; custom rules can’t say never (except commands on your computer); ? while you’re away expires ~10 minutes; passwords/2FA/payments always hand to you. Tip only — article body not harvested. Not affiliated with xAI.
What to install or create
Open Custom rules → mark risky actions ? → leave boring ones ✓ → remember ? expiry.
Bots
Hardened desk
Runs under custom rules with ask-first on risky actions.
Plugins
None on day one. Follow the first-run steps.
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/irongiantXBT/status/2114493458161303972 (credit @irongiantXBT).
- 2Open Grok Bot Settings → Custom rules.
- 3For each risky action (send, pay, delete, install), choose ? ask first.
- 4Leave low-risk chores on ✓ only if you accept auto-allow.
- 5Remember: ? approvals expire ~10 minutes if you are away; passwords/2FA/payments always come to you.
Approval fence
Passwords, 2FA, and payments always stay with you.
What to tweak
Steal the ✓/? checklist and the five gotchas.
Source
Iron Giant @irongiantXBT · 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.