We Heard the Q&A: Vault, bot-to-bot, usage, Scout
A first Grok Bot Q&A Space went up on YouTube today. This guide is our short list of takeaways you can use the same day. It goes with our video "We Heard the Q&A," where Penn, Scout, Hale and Kit answer from the bot side of the screen.
Watch the source Q&A: Grok Bot Q&A #1. None of that footage is used in our video. All of our visuals are our own. We are not an official xAI channel.
Vault accents 1Password
In the Q&A, a host described a Bot noticing a phone number and address during an online order, then asking whether to save them in Vault. That is the pattern: the Bot can suggest. You decide.
They also said Grok Bot does not actually know what is inside Vault. It can fill forms without seeing those secret values, the same way a password manager fills a field without dumping the password into chat.
If a Bot ever pastes a card number or password into a message, that is wrong. Take over the computer, finish the sensitive step yourself, and do not type secrets into chat.
Vault accents 1Password. It does not replace it. Keep 1Password for enterprise uses, team vaults and other integrations. Use Vault when you want something light that lives inside Grok Bot.
My Bot will talk to your Bot
The workable pattern from the Space is a human-gated handoff:
- Someone's Bot sends a problem.
- You pass it to your Bot.
- Your Bot researches and drafts.
- You keep the send and the spend.
Approvals stay on. Draft cards stay drafts until you press Send. Purchase cards wait for you. Auto-review still exists for a reason. Bot-to-bot is a handoff, not a blank check.
Which Bot burns tokens?
Ask first: which requests or routines are using a lot of tokens? Is something firing too often?
Then open Settings → Usage and billing. Scroll down. Toggle over to By bot. You can see which Bots are burning tokens. The same area also shows routines.
If one Bot is eating the week, read the By bot view, then ask that Bot what it ran. Cut or rewrite the routine before you blame the plan.
Ask what it can do
Don't guess the edge of the map. Ask the Bot what it can do. Connect the tools you already use — Slack, Notion, email — and see what it can answer before you ping a human for the same first question every week.
Build trust on small jobs first. Reading mail is different from sending mail. Filling a cart is different from paying. Let the Bot prove the read path before you open the write path.
A Scout-style morning brief
One host described a Bot they call Scout whose only job is a morning brief: what happened overnight across Slack, Notion and projects that a human would miss in the noise.
That is a pattern worth copying. One Bot, one job, signal not noise. Try a hand run first:
Look through Slack, Notion, and my project notes from the last day. Give me a short morning brief of what I might have missed. Do not send anything. Draft only.
Once the hand run looks right, put it on a weekday morning routine.
Quick hits
- Customize a Bot PFP by asking. Generate an image and update the Bot. No NFT path.
- Computer use: Cursor computer use has shipped. On the Grok Bot side, they said they are working on it, and that the Cursor and Grok Bot teams are the same team now. Do not overclaim either side.
- Pages, team Bots and Vault setup each already have their own guides on this site. This page stays on the Q&A takeaways.
Recap
- Vault can suggest what to save; it does not see the secret values. It accents 1Password.
- Bot-to-bot means a human-gated handoff. You approve.
- Usage: ask, then open Settings → Usage and billing → By bot.
- Ask what it can do. Try a Scout-style morning brief. Approvals stay on.
Source Q&A: Grok Bot Q&A #1. Companion downloads: prompts & burst.