Grok Bot approvals and boundaries
Unscoped write access makes Bots retry failed sends, re-navigate blocked pages, and burn computer-use tokens. Set boundaries in the request, in the Bot description, and in Auto Review rules.
Hub: Tokenminning in Grok Bot.
Set boundaries in the request
Tell the Bot what it can do and where it must stop:
Reconcile the campaign data and draft a recommended budget change. Do not change the campaign or message the agency. Ask for approval after showing current value, proposed value, and expected impact.
Prefer explicit boundaries for:
- Sending messages or invitations
- Publishing content
- Purchases and financial transfers
- Deleting or overwriting data
- Changing permissions or production systems
- Accepting legal terms
An approval controls the proposed action. It does not reverse work already completed.
Auto Review rules
When available, open Settings → General → Auto-review:
| Rule type | Effect |
|---|---|
| Require Approval | Always stop matching actions |
| Always Allow | Proceed unless another rule stops the action |
If both match, Require Approval wins.
Write narrow rules:
- Require approval before sending any external email
- Require approval before changing a production dashboard
- Always allow
git statusin/workspace/reports
Avoid broad rules such as “allow everything in the browser.” Auto Review is model-based — complement it with least privilege, not replace it.
Personal Auto-review rules live on the current desktop and sync to its Grok Bot computer. Verify them on each installation.
Local-computer execution
Under Settings → General → Agent → Execution on Local Computer:
| Setting | When to use |
|---|---|
| Ask every time | Default — approve each local command |
| Always allowed | Rare; specific local workflows only |
| Never allowed | Bots use cloud computer only — lowest local risk |
These settings do not block cloud computer use.
Draft before execute
Patterns that cut wasted retries:
| Pattern | Token impact |
|---|---|
| Read-only first pass | Bot gathers evidence before write attempts |
| Draft in conversation | You review before any external action |
| Source links required | Fewer hallucinated follow-ups |
| Stale-data stop | Bot reports failure instead of using old exports |
Align with routine design: automate preparation, keep sends and production changes behind approval.
Secrets and handoffs
For passwords, passkeys, 2FA, and CAPTCHAs:
- Open Agent Computer
- Take control
- Complete the sensitive step
- Return control and tell the Bot to continue
Do not send passwords or one-time codes in chat. Use secure secret requests for supported connections.
Review access regularly
When a project ends:
- Pause or delete related routines
- Sign out of websites on the shared computer
- Uninstall connectors and revoke authorization in the source service
- Remove sensitive files from
/workspace