Which agents work with it?

Any agent that reads skills from a directory. Claude Code, Codex and Gemini CLI read it natively; Cursor and VS Code connect over MCP.

The voice runs on your own machine, so there is nothing to meter. The first run downloads it, about 340 MB.

Yes. The skill is MIT-licensed and the authoring format is public.

Create

Grok Bot buys your conference pass from memory and asks before it emails finance

2 days ago

@grok-bot Subscribe

Grok Bot walks one request from start to finish: an expenses Bot pulls last year's pass from memory, finds the receipt in Gmail, signs in from Vault on its shared cloud computer, and stops for an Ask first rule before it emails finance. Enterprise admins also get Data Retention settings that delete idle Bots, computers and old messages. https://docs.x.ai/grok-bot/how-grok-bot-works https://docs.x.ai/grok-bot/teams-and-enterprises https://docs.x.ai/grok-bot/computers

Ask about this presentation

Show transcript

Ask your Grok Bot expenses Bot to sign you up for last year's conference and expense it. It checks memory, finds the receipt in Gmail, buys the pass, asks you once, and logs it.
Slide text
Grok Bot buys your conference pass from memory and asks before it emails finance
“Sign me up for the same conference as last year and expense it.”
01 Memory Which pass, which card
02 Gmail Last year’s receipt
03 Computer Signs in, buys the pass
04 Auto Review Asks before emailing finance
05 Google Drive Logs the expense
SpaceXAI · docs.x.ai/grok-bot/how-grok-bot-works
Your message didn't name the pass or the card. The Bot's work log has last year's pass, and its rules pick the work card. Tell any Bot your time zone, and every Bot knows it.
Slide text
Each Bot keeps its own memory, and every Bot knows your name and time zone
All your Bots
About you
Your name and time zone
Expenses Bot
Rule
Use the work card for conferences
Work log
Last year’s 2-day pass, $749
Primary Bot
Preference
Keep morning briefs short
Work log
Drafted your offsite agenda
SpaceXAI · docs.x.ai/grok-bot/how-grok-bot-works · It checks its memory
The conference site has no app, so the Bot opens it on its cloud computer. Each Bot gets its own screen there, and when one Bot signs in, your other Bots are signed in too.
Slide text
All your Bots share one cloud computer, and one sign-in counts for all of them
Your Bots’ computer
Browser · command line · files that stay between tasks
Expenses Bot’s screen
Primary Bot’s screen
You, watching any screen live
SpaceXAI · docs.x.ai/grok-bot/how-grok-bot-works · It signs in and buys the pass
For a password, the Bot tries Vault, then 1Password, then sends you a Secure Form. Whichever it uses, the login goes straight into the page, and the Bot never sees it.
Slide text
The Bot fills a login from Vault, then 1Password, then asks you
01 Vault Logins you saved for your Bots
02 1Password Logins you approve there
03 Secure Form Asks you, then fills the page
SpaceXAI · docs.x.ai/grok-bot/how-grok-bot-works · It signs in and buys the pass
Auto Review checks each action first, and most run on their own. Write your own rule in plain words, like send an email, and an Ask first rule always stops it for your approval.
Slide text
An Ask first rule stops the email to finance until you approve it
Custom Rules
Where Settings → General → Bot
Rule “send an email”
Choose Ask first or Allow automatically
Default Auto Review on; most actions run
SpaceXAI · docs.x.ai/grok-bot/how-grok-bot-works · It asks before it emails finance
For an app outside the catalog, ask a Bot to connect its MCP server. If the service only has an API, tinkabot builds the server, tests it, and publishes it only when you say so.
Slide text
tinkabot turns a service’s API into an MCP server your Bots can use
01 API A service with no MCP server
02 tinkabot Wraps it in a plugin with skills
03 Tested Before anything ships
04 Published Only when you say so
SpaceXAI · docs.x.ai/grok-bot/how-grok-bot-works · Add your own tools
Your Bots share the computer's files and sign-ins. After this request, every Bot is signed in to the conference site and can use the work card. Keep Ask first rules on anything you can't undo.
Slide text
Your Bots aren’t separated from each other
After the conference request
Conference site Every Bot is signed in
Work card in Vault Every Bot can use it
Auto Review Lowers the risk, doesn’t remove it
SpaceXAI · docs.x.ai/grok-bot/how-grok-bot-works · Security
Enterprise admins get three Data Retention settings, all off by default. They delete idle Bots, idle computers with their disks, and old messages. Bot owners get 30 days' warning by email, and deleted data can't be recovered.
Slide text
Enterprise admins can now delete idle Bots, computers and old messages on a timer
Bots
Deletes
Unmessaged Bots, with memories, skills and routines
Period
60 to 365 days
Computers
Deletes
A member’s idle computer and its disk
Period
30 to 365 days
Messages
Deletes
Messages and attachments past the age
Period
30 to 365 days
SpaceXAI · docs.x.ai/grok-bot/teams-and-enterprises · Data retention
Your primary Bot coordinates the others, and a Bot with one job builds memory for it. I'd start there, and add Ask first rules for sending, publishing and deleting before saving a card.
Slide text
Start new work in your primary Bot, and give a repeating job its own Bot
Read next
Page How Grok Bot Works
Link docs.x.ai/grok-bot/how-grok-bot-works
Set up several Bots dr eggbot, one job each
SpaceXAI · docs.x.ai/grok-bot/how-grok-bot-works · Best practices