Grok Bot computer and apps
Grok Bot works from a persistent cloud computer with browser, command line, and files. Computer-use steps bill separately from chat turns and often cost more than a connector call.
Hub: Tokenminning in Grok Bot.
One computer, all your Bots
Every Bot on your account shares:
- Browser cookies and signed-in sessions
- Files on the VM
- Command-line credentials
One Bot can continue from work another Bot saved. Treat a login or file on the computer as available to all your Bots — not isolated per Bot.
Each Bot gets its own screen on the shared computer. Several Bots can use browser and desktop tools in parallel, but one Bot runs only one computer-use task on its screen at a time.
Connectors before browser
Plugins (connectors) give structured access to supported services:
- Settings → Plugins → browse and add
- Authenticate in your browser if requested
- In chat, type
@to attach the connector; type/for a saved skill
Prefer a connector when one exists — it is usually more reliable than clicking through a website. Use the browser for services without a connector or for visual workflows a connector does not expose.
Installed connectors are account-wide, not isolated to one Bot. Disable connector tools you are not using to reduce schema overhead on planning turns.
Work with files
Durable project files belong in /workspace with clear folder names. Ask Bots to copy important results there or attach them to the conversation.
Treat temporary directories and uncommitted application state as replaceable. After a task, remove sensitive temporary files — they remain visible to every Bot.
Sign in once, sign out when done
Browser sessions persist across tasks. Signing in for one Bot makes the session available to others. When a service should no longer be accessible, sign out on the shared computer and revoke the connector in the source service.
Watch without blocking
Open Agent Computer from a conversation to preview clicks, typing, and status. Closing the Grok Bot app or your laptop does not stop cloud work — including routines.
Take over only for passwords, 2FA, CAPTCHAs, or payment checks. Do not paste secrets into chat.
Recovery and reset
From Settings → Beta:
| Action | Effect |
|---|---|
| Update Agent Computer | Rebuild with latest image; preserve durable state |
| Recover Agent Computer | Replace unreachable VM; preserve durable state when offered |
| Reset Agent Computer | Return to durable snapshot; may discard recent unsaved work |
Wait for active work to finish before recovery when possible.
Local computer is separate
The cloud VM is not your Mac or Windows machine. Local execution requires explicit approval under Settings → General → Agent → Execution on Local Computer. Default Ask every time; use Never allowed unless a Bot has a specific local reason.