xAI's documentation for Grok Bot outlines various settings for app-wide and desktop-local behavior, as well as conversation details for individual Bot profiles and notifications. These settings are accessible through the account menu or by pressing Cmd/Ctrl+,.
The documentation also addresses security and privacy, emphasizing user control over sensitive inputs and consequential actions through approvals and secure handoffs. Grok Bot is designed to complete work while keeping these aspects under user control.
Key Points
- Grok Bot settings manage app-wide and desktop-local behavior, along with individual Bot profiles and notifications.
- The Grok Bot settings dialog sections may vary based on the user's account and rollout.
- Execution on Local Computer controls whether Bots can run commands on the desktop, with per-command approval as the default.
- Auto Review rules shape which actions require user approval and are stored on the current desktop, synced to its Grok Bot computer.
- All Bots on a user's account share a single persistent cloud computer, meaning files, browser sessions, and command-line credentials are available across the Bot roster.
- Plugins, now called Connectors, are account-wide and their availability is not isolated to one Bot.
- For sensitive information like passwords or one-time codes, the Bot should hand control to the user, and values entered into secure secret requests are masked and excluded from the transcript.
Context
According to xAI, Grok Bot's settings allow users to configure aspects such as appearance (Light, Dark, Follow System) and manage plugins and packaged skills through a Marketplace. The documentation also details how usage and billing information is displayed, including weekly included usage and on-demand usage for eligible accounts. For team and enterprise plans, Team Setup shows managed configurations provided by administrators.
Why It Matters
Understanding Grok Bot's settings and security features is crucial for builders and users to manage the behavior of their Bots effectively and maintain control over their local and cloud computing environments. The shared nature of the cloud computer and the controls for local execution directly impact data isolation and security practices.
What To Do
- Review the Grok Bot documentation on "Approvals, security, and privacy" before changing Execution on Local Computer or Auto Review settings.
- Note that Auto Review rules are model-based and should complement, not replace, least privilege and explicit approval boundaries.
- Be aware that personal Auto Review rules are stored on the current desktop and synced to its Grok Bot computer, requiring separate verification on other desktop installations.
- Avoid placing sensitive information, such as secrets, customer data, or internal URLs, in a Bot that will be shared publicly.
- Familiarize yourself with the Grok Bot documentation regarding the shared cloud computer to understand how files, browser sessions, and credentials are made available across all Bots on an account.