How Grok Bot works: computer, memory, skills, approvals and Team Bots
A Grok Bot combines a job description with memory, skills, routines, connected apps and a shared cloud computer. Auto Review checks actions before they run, and your Ask first rules stop anything you want to approve. Bots can hand work to each other, and Team Bots let a whole team share one Bot.
The shared cloud computer
Every Bot on your account works on one persistent cloud computer with a browser, files and a terminal. Each Bot gets its own screen, so several can work at once, and you can watch any screen live. A login made by one Bot is available to all of them.
That sharing is useful for handoffs but it is not a security boundary: treat anything on the computer as visible to every Bot, and sign out of services a Bot no longer needs.
Memory: what a Bot carries into every run
Each Bot keeps its own preferences, standing rules and a dated work log. A few facts, like your name and time zone, are shared by all your Bots. You can ask a Bot what it remembers, correct it or tell it to forget something.
Memory is for rules and preferences, not data. Long lists belong in files, logins and cards belong in the Vault, and changing numbers like prices should be looked up fresh each time.
Skills: saved recipes
A skill is a reusable set of instructions: when to use it, inputs and access, the steps, how to check the result, what to return and what needs approval. Ask a Bot to save a process that just worked as a skill.
Where available, Teach a task lets you demonstrate a browser workflow (up to ten minutes, no microphone) and the Bot drafts a skill from it. Review and test the draft before scheduling it.
Routines: work on a schedule or trigger
A routine tells one Bot when to run a workflow: on a schedule such as "every weekday at 8:00 AM," or when something happens, like a Slack message, an email to the Bot, a GitHub, Linear, Sentry or PagerDuty event, or a webhook call. See our skills and routines guide for setup and testing.
Approvals: Auto Review and Ask first rules
- Auto Review is on by default and checks commands, app actions and computer actions before they run. Most go ahead; risky ones show an approval card.
- Add your own rules in Settings, General, under Bot, Custom Rules. Describe an action like "send an email" and choose Ask first or Allow automatically.
- Only your own messages count as instructions. Hidden text on a web page or in an email is not treated as a request from you, though the docs warn this lowers the risk rather than removing it.
- Approvals from work that started without you, such as a routine, expire after about 30 minutes.
Vault and secure sign-in
Bots look for logins in the Vault first, then 1Password, then a Secure Form that asks you. The login is filled into the page and the Bot never sees it. Cards saved in the Vault fill at checkout; if you want to approve every payment, do not save the card. Passkeys, single sign-on and CAPTCHAs are handed to you through a computer takeover.
Templates and Team Bots
A template shares a Bot as a recipe, not a clone: the recipient gets its identity, description, skills and routines, never your computer, logins or chat history. Strip secrets and internal details before you publish a public link.
A Team Bot is one Bot that a team shares, with private chats per person. Team Bots are available on Team and Enterprise plans and always run in the cloud.
Bots that talk to Bots
Bots can message each other and work together in group chats. A common pattern is a set of specialists (inbox, calendar, research) plus one hub Bot that collects their results and is the only one that messages you. Add a hub once you have three or more Bots; before that it is overhead. Our builder has a team mode that writes the hub instructions.
FAQ
Do my Bots each get their own computer?
No. Per the official FAQ, every Bot on your account uses one shared cloud computer, with its own screen per Bot. Do not use separate Bots as a security boundary.
Can I choose which AI model a Bot uses?
No. The FAQ says Grok Bot picks the model for each task and there is no model picker.
What is the difference between a skill and a routine?
A skill describes how to do a task. A routine assigns a workflow to one Bot and says when it runs, on a schedule or after an event.
Related Grok Bot news
- Grok Bot can now join Tailscale tailnets to reach private MCP servers
- Grok Bot on Mac can now use Messages, Mail, Notes, Reminders, Calendar, Location and Contacts
- Grok Bot can now join meetings, now listed for Super plans too
Keep learning
- Grok Bot skills and routines: schedules, triggers and testing
- Grok Bot connectors and apps: Gmail, Slack, Notion, X, MCP and more
- Grok Bot instructions best practices: 12 patterns for reliable Bots