xAI's documentation for Grok Bot details its operation on a persistent cloud computer. This setup allows the bot to use a browser, command line, files, and connected tools without requiring the user's laptop to remain open. The cloud computer is assigned to a user account, not to individual bots, meaning all bots under one account share the same computing environment.
Key Points
- Grok Bot operates from a persistent cloud computer, not a local machine.
- The cloud computer provides a browser, command line, file system, and connected tools.
- All bots within a user account share the same cloud computer, including browser sessions and installed connectors.
- Each bot receives its own screen on the shared computer, allowing parallel use of tools, though only one task can run per screen at a time.
- Users can view the shared desktop via "Open Agent Computer" from a conversation, which shows clicks, typing, navigation, and status.
- Connectors, presented as Plugins, offer a structured and often more reliable way to interact with supported services compared to browser-based clicking.
- Durable project files should be stored in the shared
/workspacedirectory using clear project folders.
Context
According to xAI, the shared nature of the cloud computer means that credentials or files placed on it are accessible to all bots on the account. Browser sessions persist across tasks, and signing in for one bot makes the session available to others. Users can take control of the computer to complete blocked steps, with secure secret requests handled separately to prevent exposure in chat.
Why It Matters
This architecture impacts how users manage data, security, and workflow continuity when deploying Grok Bot. The shared environment necessitates careful consideration of sensitive information and provides a consistent operational state across different bot tasks.
What To Do
- Note that any credential or file placed on the cloud computer is accessible to all bots on your account.
- Prefer using connectors when available, as they are often more reliable than web-based interactions.
- Store durable project files in the
/workspacedirectory to ensure they persist across computer updates and recoveries. - Review the "Approvals, security, and privacy" section for details on local-computer permissions if enabling such capabilities.