Getting started with Grok Bot
Grok Bot is an agent with a computer. Learn how to stand one up, chain specialists, and run the workflows I actually use.
Break the work into roles, handoffs and acceptance checks. Use the following task arrangements as practice scenarios, and verify results in your own setup.
Grok Bot is an agent with a computer.
Using it feels like texting a colleague, except that colleague has a real, persistent desktop. It can do what you can: use apps, browse the web, write and run code.
What is Grok Bot?
Grok Bot is a personal assistant that can take any action on a computer.
The computer lives in the cloud. It has a desktop, a filesystem, a terminal, and apps. If you click the bot's window, you can use that machine like a remote desktop. The bot has the same access you do.
Because it has a real computer, you can teach it a workflow by recording a task or by writing a prompt. you asked it to look at Costco and Amazon, add things to your cart, then compare prices, delivery charges, and times.
When a flow needs you, the bot can hand the desktop back the same way a remote computer would. you fill in a CAPTCHA or a 2FA login. It can also send you a secure form for a password or an API key.
It also runs in the cloud, so you get the same computer from your phone and your desktop. your Marketplace bot can search Facebook for a variegated Monstera Albo because Facebook is already logged in.
Anatomy of a bot
you like to start from a voice note. A bot is a set of instructions, so you can define it however you think.
Behind the scenes, settings are three fields:
Name: Tech Demos
Title: Daily X tech scout
Description: Look at my bookmarks each weekday, pick one technology worth demoing, draft a prompt in my style, wait for approve or deny, then kick a Cursor cloud agent.You can set these in chat or in Settings, top right.
Be as specific as you can. Describe a workflow exactly as you would do it, or record a demo on your screen. Then assume the bot can do hard things AI usually can't.
you call Tech Demos your DevRel bot.
Each weekday it scouts your X bookmarks for new technology, drafts a prompt for a prototype, and asks you to approve it.
you tweak the prompt, approve it, and the bot starts a Cloud Agent through the Cursor connection. you can open the build in Cursor immediately.
When it's done, the bot sends screenshots or a clip and opens a PR.
Grok Bot supports the same MCP servers, plugins, and skills as Cursor. you have Gmail, Google Calendar, Google Drive, and others. You can connect multiple accounts per service, so you can look through personal and work email, or check more than one Slack.
If you are wondering whether you can do something, ask.
Using Grok Bot
There are three ways to talk to a bot.
- Chat: Send it a message.
- Routines and triggers: A bot can set its own schedule or listen for events from other apps. It can watch a Slack thread or a GitHub PR.
- Other bots: Bots can message each other and trigger each other.
Permissions and a shared computer
If you log into Amazon on a computer the agent can use, it can technically buy whatever it wants, the same way a human could.
Bots are kept in check by permissions, a reviewer, and allow/block lists. You write the rules in natural language in Settings > General > Agent. A separate review agent checks proposed actions and can allow, block, or escalate to you. Allow and block lists steer that reviewer. You are trusting the model to follow what you wrote. The work still happens in an isolated environment.
Most of us are used to defining agent rules in code or JSON. With Grok Bot, the rules are a prompt.
One more thing: if you log into a site with one bot, every other bot can reach that site too.
Multi-bot chains
you treat bots as specialists. Because they can talk to each other, one specialist can ask another for help.
You can drop several into a group chat. A weekday routine can route a request through different bots until the job is done.
your Marketplace bot watches Facebook Marketplace and Craigslist for espresso machines.
When it needs a judgment call, it can ask your Chief of Staff bot.
Four bot workflows you’m loving
A personal CRM
you built this on your phone in 10 to 15 minutes.
The prompt: turn the people you already follow on X into a private personal CRM in Notion, using only public profile information.
you follow roughly 800 to 900 people. The board has profile images, descriptions, and a link back to each public profile.
When you travel, you can use it to reconnect with people you already know and ask if they want to grab a coffee.
you are the annoying coffee guy.
Anything you would do by hand on LinkedIn or X, you give to a bot. Anything you would feel bad about asking an intern to do, you give to a bot.
Arnold, your fitness bot
you already had a strength training app that you vibe-coded. It took weeks of work. It was useful, but time-consuming, and it still broke routinely. One day you asked, “what if this was a bot?”
you moved it into chat.
Arnold is your strength and hypertrophy programming coach. you broke the old app into MCP servers, skills, and plugins by chatting with Grok.
Grok Bot built the infrastructure from... inside Grok Bot.
The core functionality is the same, but the end state is much more minimal: less maintenance, fewer bugs, and zero headaches.
The feedback loop is also faster than the old app. Updates to the logic or behavior are now just chatting with a bot: the same interface as using the app itself.
If you can decompose an app into inputs, logic, and a datastore, you can probably turn it into a bot. You may find that a better solution than vibe-coded software.
Writing code with Grok Bot
your outer loop agent gathers context from Slack, Notion, GitHub, and docs, then hands a clean prompt to a Cursor cloud agent for the inner loop that actually builds software.
If you ask one agent to read files, debate what to build, then immediately delegate the fix, that agent carries a bunch of dirty context.
Using an agent in the “outer loop” is one way to keep dirty context out of the “inner loop” executors that actually do the work.
Define project rules for design, code review, architecture and product decisions. Use capabilities that are installed and documented in your own setup, checking inputs, permissions, scope and outputs first.
An important distinction: Grok Bot is not writing the code. It is creating the same prompts you would, then sending them to a specialized coding harness that lives inside Cursor.
Search across Slack, Notion, GitHub
If your company has Notion, Slack, and a wiki, finding things while you answer email is hard.
you routinely ask Grok Bot how Grok Bot works. It reads the codebase, checks discussion on Slack, scans design docs in Notion, and gets you the answer.
you now ask more questions of Grok Bot than you do of your coworkers! That feels good, because you can respect their time and cut Slack fatigue.
What’s next
Grok Bot is an agent with a computer in the cloud. It can write and run code, run software, do workflows, and control the computer the same way you can.
The main difference from a lot of other personal agents is zero setup. More and more, you can replicate a workflow just by asking Grok Bot.
So what you create is limited not by what Grok Bot can do, but by what you can imagine giving it. Give it a shot. you’m excited to see what you’ll build.
学完后记得保存进度
Completion marks stay in this browser. Sign in to remember your last chapter and reading position.