Open Grok Bot settings

Grok Bot settings cover app-wide and desktop-local behavior. Each Bot’s profile and notification preference live in that Bot’s conversation details instead. Open settings from the account menu or with Cmd+,. Official guide: Settings and notifications.

Settings sections depend on your account and rollout, so some options below may not appear for you. Do not invent controls that are missing from the docs page for your plan.

General

• Account. Sign in or out of the Cursor account Grok Bot uses. The account menu also shows the installed version and a link to the iOS app.
• Appearance. Follow System, Light, or Dark.
• Agent. The time zone routines use for schedules, plus Execution on Local Computer. Cursor manages model selection, so there is no model picker.
• Auto-review. Your personal Auto-review rules, plus any team rules your admin requires.

Execution on Local Computer controls whether Bots can run commands on the desktop in front of you. Per-command approval is the default, and the setting applies to that desktop alone. Auto-review rules shape which actions stop for your approval. When your admin enforces Auto-review for the team, locked team rules appear with “Required by your admin. You can't edit or delete this rule.” Members can add their own rules on top, and those only make behavior stricter; Ask first wins when rules conflict. Personal rules are stored on the current desktop and synced to its Grok Bot computer, so another desktop installation needs its own copy. Read Approvals and Auto Review in the security docs before you loosen either control.

Computer

Turn on Route egress through this desktop when the cloud computer’s web traffic should leave through the machine in front of you. Destinations see that desktop’s IP address, and the Bot can reach networks available from that device. The setting applies to one desktop. If an Enterprise admin turns off Allow Local Egress, the toggle turns off and locks; any active route stops within five minutes, and your choice returns when the admin re-allows local egress. For private network options see the Connect to private networks docs.

Plugins, usage, and team setup

Plugins opens Marketplace to discover plugins and packaged skills, and Yours to review installed plugins and private skills. An installed plugin may still need browser authentication, and individual plugin tools can be enabled or disabled. On Teams and Enterprise plans, team-provided plugins may be required or restricted by an admin.

Usage and billing shows weekly included usage and on-demand usage for eligible accounts. The account menu can also show weekly usage at a glance.

Team Setup is Enterprise only. When an Enterprise admin provides a managed setup, you review or reinstall it here. Admins configure manifests from the dashboard.

Updates

Update controls live in the Beta section of settings. The Grok Bot app and the Agent Computer update separately:

• Check for Updates and Restart to Update update the desktop app.
• Update Agent Computer rebuilds the cloud computer on the latest image while preserving durable state.
• Reset Agent Computer is a last resort that returns the computer to its synced durable state; unsynced recent work does not come back.

Use the least destructive recovery order from Work with Grok Bot before you reset.

Per-Bot settings live elsewhere

Click the Bot’s name at the top of the chat (View conversation details), then choose Bot settings, to edit one Bot’s name, label, description, and notifications preference. Click the Bot’s picture in the same panel to change its avatar. Those fields belong to that Bot alone. For the profile fields see Edit a Grok Bot profile. For the per-Bot notification switch see Turn on notifications for a Grok Bot.

Pitfalls

• Editing app-wide Settings when you meant one Bot’s name, description, or notifications — those live under View conversation details → Bot settings.
• Turning on local execution or Route egress without reading the approval and network docs — both change where commands run and which networks the Bot can reach.
• Using Reset Agent Computer before Retry, app restart, Recover, or Update — reset drops unsynced work.
• Expecting every section listed here to appear on every account — rollout and plan control which rows show.