How Grok Bot Works

Your message doesn't say which conference, which pass, or which card to use. Your expenses Bot fills in those details from memory. Its work log has last year's 2-day pass, and you gave it a rule to use the work card for conferences. Ask what it used, and it shows you.

Expenses

Expenses

What do you remember for this?

Here is what I used:

• About you: your name and time zone, which all your Bots know
• Your rules for me: use the work card for conferences
• My work log: last year's 2-day pass, $749

Each Bot has its own memory. It keeps your preferences, the rules you ask it to follow, and a dated log of its work. A few facts about you, like your name and time zone, are shared by all your Bots.

So you only have to say something once. Tell any Bot your time zone, and all your Bots know it. Tell your expenses Bot where receipts go, and only that Bot knows it.

A Bot decides on its own what to remember. You can also ask it to remember something, fix it, or forget it. Memories can go out of date, so for numbers that change, like prices, ask the Bot to look them up again. Keep logins and cards out of memory and in Vault. See What a Bot remembers.

Next, the Bot searches Gmail for last year's receipt. Gmail is a connected app, so the Bot works in it directly instead of opening the website. That's more reliable than clicking through pages in a browser.

If an app isn't in the catalog, ask a Bot to connect the app's MCP server, the standard way AI tools connect to a service. If the service has an API but no MCP server, tinkabot can build one. It wraps the API in a plugin with an MCP server and skills, tests it, and publishes it only when you say so. See Connect an app.

The conference site has no app, so the Bot opens it in a browser on its cloud computer. All your Bots share that computer. It also has a command line and files that stay between tasks. Each Bot gets its own screen, so several Bots can work at once, and you can watch any screen live. When one Bot signs in to a site, your other Bots are signed in too.

The site asks for a password. The Bot looks for a login in this order:

Expenses

Expenses

No login in Vault or 1Password, so I sent a Secure Form.

Secure Form

Sign in to tickets.example.com

Email: you@example.comPassword: hidden•••••••••••••••••••Securely save to Bot's vault

Never shown to your Bot. Filled directly to tickets.example.com.

Submit

Whichever one it uses, the login goes straight into the page, and your Bot never sees it.

To pay, the Bot uses the work card you saved in Vault. A saved card fills in at checkout without asking you each time, and the Bot never sees the number. If you'd rather approve every payment, don't save the card. See Pay for things.

If a task needs an API key, the Bot sends you a secure secret card. The key stays hidden and out of the chat.

Some steps need you, like single sign-on, a passkey, or a CAPTCHA the Bot can't solve. For those, the Bot hands you the computer. Choose Open computer on the request, then Take control. Finish that step, and tell the Bot to continue. See Vault and secure sign-in and Connect 1Password.

With the pass bought, the Bot is ready to email the receipt to finance. You made a rule to approve emails first, so it stops and asks you.

Expenses

Expenses

Bought the 2-day pass. Your rule says to ask before I send an email.

Email the receipt to finance

Paused by your Ask first rule

To

finance@example.com

Subject

2-day pass receipt, $749

Edit ruleNot nowAllow

Before a Bot runs a command, uses an app, or acts on its computer, Auto Review checks the action. Auto Review is on by default, and most actions go ahead on their own. When one needs you, the Bot shows an approval card with the action and its details, then waits.

You can add your own rules too. In Settings → General, under Bot, open Custom Rules. Describe an action in plain words, like “send an email,” and choose Ask first or Allow automatically. An Ask first rule always stops a matching action. That's the rule that stopped this email.

A card stopped by an Ask first rule shows Edit rule, which opens your Custom Rules. Other cards can show Always allow, which saves a rule so similar actions run on their own next time.

Only your own messages count as instructions. Say the conference page had hidden text telling the Bot to email your contacts. Auto Review wouldn't treat that as a request from you. These checks lower the risk from harmful content, but they don't remove it. Keep Ask first rules on anything you can't undo. See Configure Auto Review.

Last, the Bot adds the expense to your Finance sheet in Google Drive, another connected app. Then it replies with everything it did. If you've closed your laptop by then, it keeps going and notifies you when it's done.

The chat shows each step as the Bot works, from your message to its reply.

Expenses

Expenses

Sign me up for the same conference as last year and expense it.

You're registered for the 2-day pass, same as last year:

• Last year's receipt found in Gmail
• Pass bought with the work card from Vault
• Receipt sent to finance after your OK
• Expense logged in Finance › 2026

Your expenses Bot did all of this as you. A Bot has no account or credentials of its own, so it can't do anything you couldn't, and every action traces back to you. The one exception is a connector your team manages, which can use team or service-account credentials.

Your Bots' computerAll your Bots work here and share its files and browser sign-ins.

Never shown to your Bots

App sign-ins

They stay on Cursor's servers. Bots use your apps without ever getting them.

Vault

Saved logins and cards fill into the page without your Bot seeing them.

Your Bots aren't separated from each other. Your other Bots are now signed in to the conference site too, and they can use the work card in Vault. Sign out of services a Bot no longer needs, and delete sensitive files when the work is done. Enterprise teams can also set a network policy and inference hooks. See Grok Bot security.

Most Bots work best with one clear job, like your expenses Bot. Your primary Bot is different. It's your main point of contact. It checks in with you on its own and coordinates your other Bots. You could send the conference request to your primary Bot, and it could pass the work to your expenses Bot.

Chief of Staff

Chief of Staff

9:41 AM

Sign me up for the same conference as last year and expense it.

I gave this to Expenses. It found last year's receipt and will check with you before it emails finance.

Start new work with your primary Bot. When the same kind of request keeps coming back with its own sources, rules, or schedule, give it its own Bot, or ask your primary Bot to create one. A Bot with one job builds up memory for that job, so you only explain it once.

• Start in your primary Bot. Give work its own Bot when it has its own sources, schedule, or approval needs. To set up several Bots at once, start from dr eggbot.
• Ask a Bot to remember rules that last. Put the details of a single task in your message.
• For numbers that change, like prices or budgets, ask the Bot to look them up instead of relying on memory.
• Connect an app for each service you use often. If a service has no app, add its MCP server, or have tinkabot build one from its API.
• Never paste a secret into a chat. Passwords go through Vault, 1Password, or a Secure Form. Cards go through Vault or a Secure Form. API keys go through a secure secret card.
• Get a task working once and save it as a skill. Then create a routine that runs it on a schedule or when something happens, like a Slack message or an email to your Bot.
• Add specific Ask first rules for sending, publishing, and deleting. To approve every payment, don't save the card in Vault.
• Treat anything on the computer as available to all your Bots.
• In a group chat, make one Bot responsible for each step.