Set Grok Bot local execution policy with the Admin API

Bots can run commands and move files on a member’s own machine through the desktop app. That path is separate from work inside the hosted cloud computer. Official guides: Admin API → Grok Bot capabilities; Grok Bot security → Local execution; Approvals, security, and privacy → Control access to your local computer.

There is no dashboard control for the team ceiling today. The Admin API localExecution field is how admins set a team-wide ceiling. Members still pick their own preference under Settings → General → Agent → Execution on Local Computer, within that ceiling.

Member default (every plan)

On the desktop app:

1. Open Settings → General → Agent → Execution on Local Computer.
2. Choose Ask every time (default), Always allow, or Never.
3. Prefer Never unless a Bot has a specific reason to touch local files.

These settings do not block the hosted cloud computer.

Team ceiling via Admin API

Authenticate with a team Admin API key (Basic auth, key as username, empty password). Reads need read:* or admin:*; writes need admin:*. Rate limit: 20 requests per minute per team per endpoint.

Read current capabilities

curl -X GET https://api.cursor.com/grok-bot/capabilities \
  -u YOUR_API_KEY:

Example response:

{
  "enabled": true,
  "cloudAgents": true,
  "templateSharing": "team_only",
  "actionRecording": false,
  "localExecution": "ask"
}

localExecution values:

Value	Meaning
never	Members cannot run local execution
ask	Local commands stay behind approval
always	Local execution may run without per-command approval (member still subject to Auto Review / other gates)
null	No team ceiling

Set the ceiling

curl -X PATCH https://api.cursor.com/grok-bot/capabilities \
  -u YOUR_API_KEY: \
  -H "Content-Type: application/json" \
  -d '{
    "localExecution": "never"
  }'

Omitted fields stay unchanged. enabled is read-only on this route — use /grok-bot/enable or /grok-bot/disable instead. Some fields return 403 when the team plan does not include them.

Clear the ceiling:

curl -X PATCH https://api.cursor.com/grok-bot/capabilities \
  -u YOUR_API_KEY: \
  -H "Content-Type: application/json" \
  -d '{ "localExecution": null }'

Security baseline

For security-sensitive rollouts, Cursor’s recommended admin list includes setting an explicit local execution policy and deciding whether Bots may act on member machines at all. Pair localExecution: "never" (or "ask") with Auto Review team instructions, Network Controls (Enterprise), and clear request boundaries from members.

Pitfalls

• Looking for a Local execution toggle on the Grok Bot dashboard page — the team ceiling is API-only today.
• Confusing local execution with Auto Review — Auto Review covers work inside the hosted computer; local execution is the member-machine path.
• Setting always org-wide without a clear need — prefer ask or never.
• Using a read:* key for PATCH — writes require admin:*.