agentos.guide › blog
Grok Bot for research slots into an Agent OS as the field researcher: your agent decides the question and the rules, and Grok Bot goes and reads public X, the web and your files on its own cloud computer.
You'll get a quick start, five copy-paste prompts and a weekly rhythm below.
Each step maps to xAI's computer and apps docs, the files and results page and the skills and routines guide.
Fancy a hand fitting it to your business? Get your Backlink Gameplan with my team, or try Polar Rank free for 3 days.
Your Agent OS holds the context: your market, your rivals, the format your team likes and the questions that matter this quarter.
Grok Bot does the legwork: every Bot you own shares one cloud computer, each on a screen of its own, and it keeps working with your laptop closed.
It's also where approval cards turn up, so nothing your Agent OS plans gets sent or posted without a click.
| Task | Agent OS | Grok Bot |
|---|---|---|
| Research question | Writes and sharpens it | Works through it |
| Source rules | Sets them once | Follows them and links every claim |
| Public X | Picks accounts and topics | Searches and reads, read-only |
| Websites | Lists the sites to check | Opens them in its browser |
| Final call | You, after opening the key links | |
A durable research Bot starts with a clear brief: the job, the sources, the output and the limits.
Give your Agent OS this, then paste its answer into the Grok Bot chat and ask the Bot to remember it.
Write a standing brief for a Grok Bot called "Researcher" for my business.
Job: answer one research question per request, using public X, the websites I list and files I attach.
Output rules: a Google Doc with headings; a direct source link and the date read after every claim; then separate lists for facts found, inferences, actions done, actions awaiting approval, open questions; then a "Could not verify" section.
Limits: read only. Never send, post, buy or sign up. If a site asks for a login or a check, stop and tell me.
Keep it under 200 words.
The five-list split and the evidence ideas come from xAI's files page, which suggests both for consequential work.
Bots read what's public on X without you connecting an X account, and the access can't post or sign in as you.
Search public X for posts from the last 14 days about [topic] and about [our brand].
Count roughly how many recent posts mention each, open the most-quoted posts, and group what people ask for or complain about.
Link every post you rely on. Keep what posters said apart from your own read of it.
Return a short Google Doc. Do not reply, like or post anything.
Reaching your own DMs, bookmarks and home timeline means adding the X plugin, and that plugin draws on X API credits from your developer account.
If your X account is based in the UK or the EU (or in Australia, Norway, Iceland or Liechtenstein), tagging @bot isn't switched on yet, so start the scan from the Grok Bot app instead.
🔥 Want the full research prompt library?
Inside the AI Profit Boardroom: step-by-step video trainings, the installable Agent OS, four coaching calls a week and 3,400+ members swapping research prompts.
There's no separate web-search tool or deep-research mode in the docs; web work is the Bot driving the browser on its cloud computer.
Open the websites of [rival 1], [rival 2] and [rival 3].
Note anything launched, renamed, repriced or announced in the last 7 days, with a link to the exact page and the date you read it.
Save each changed page as a PDF in /workspace/rival-check/[date].
If a page needs a login, a passkey or a CAPTCHA, stop and hand me the computer.
Saving a page as a PDF from the Bot's browser arrived in v0.70.2, per the Grok Bot changelog.
For more on how the browser behaves, see our Grok Bot browser guide.
Attachments cover PDFs, Word, Excel and PowerPoint, CSV, JSON, YAML, HTML, email files and notebooks.
xAI's advice is to say what each file is and how the Bot should use it.
The CSV is last quarter's customer survey. The two PDFs are our rivals' service brochures.
Find the five most common requests in the survey, check which ones each rival already covers, and build a Google Sheet with columns: request, count, rival coverage, source file, page number.
Do not change the original files. Finish with a two-line recommendation followed by the evidence.
Google Sheets edits only work on sheets the connected account can edit; a file shared as Viewer stays read-only.
Where Pages has reached your account, the Bot can turn findings into a page with tables, charts, filters and switches, kept in its Library.
Make a page called "Weekly market brief" from this week's X scan, rival check and survey sheet: a summary, a table of changes with links, and a filter by rival.
Then set up a routine: every Monday at 8:00 AM, rerun Prompts 2 and 3, update the same page, and post a link in this chat.
If a source has nothing new or won't load, say so on the page instead of reusing last week's data.
Pages is rolling out gradually and isn't on Enterprise teams yet, so use a Google Doc there instead.
A new routine waits for its next slot, so press Test once to see a real run.
For a bigger piece of work, ask your primary Bot to set up three Bots and put them in a group chat.
xAI's collaboration docs suggest one owner per stage: a researcher that collects material and links each claim, a writer that drafts from the findings, and a reviewer that checks the draft against the sources and reports only blocking problems.
Tell the group not to publish anything.
Two things trip people up: approval cards don't appear inside a group, and handoffs into the group are text only, so images should go straight from one Bot to another.
Keep shared drafts in the project folder under /workspace, which every Bot can read.
📞 Want a second pair of eyes on your research setup?
Get your Backlink Gameplan and my team will help you pick the first question and the right sources.
The finished research prompts live inside the AI Profit Boardroom, and if you'd rather talk it through, get your Backlink Gameplan from my team, or try Polar Rank free for 3 days.
Prompt 1, so the Bot has a standing brief with the output rules and limits. Then run Prompt 2 or 3 by hand once before you schedule anything.
Yes, by asking. Put the source-link rule and the "Could not verify" section in the brief, because the docs describe no automatic citations.
Pages is rolling out gradually and is not on Enterprise teams yet. Ask for a Google Doc with the same sections instead.
Yes. Routines run in the cloud on the Bot's computer, so closing your laptop does not stop them.
Paste the five prompts, check the links each Monday, and join the AI Profit Boardroom to run Grok Bot for research in your Agent OS.
About Julian
I'm Julian Goldie, an AI entrepreneur, SEO expert and the founder of the AI Profit Boardroom, which has 3,400+ members.
I help business owners scale with AI agents, automation and SEO.
My YouTube channel has 400,000+ subscribers, and I run Goldie Agency, a seven-figure SEO agency.
→ Grok Bot Browser In Your Agent OS: A Quick Start, 5 Copy-Paste Prompts And A Weekly Web Workflow
→ Grok Bot AI Full Course (Step By Step)
The installable system behind every guide on this site — dashboard, agents, memory and pipelines — updated as new tools land, with 3,400+ members and four coaching calls a week.
Join the AI Profit Boardroom →📺 Video notes + links to the tools 👉
🎥 Learn how I make these videos 👉