How to create your first Grok Bot teammate (2026)
Grok Bot is not the grok.com chat. It is a named teammate with memory and a cloud computer. This flow matches current docs: plan, desktop, first job with a human OK.
The problem it solves
Delegating to a chat does not finish the work in the CRM, the admin or the PDF. Grok Bot exists to finish in real apps, with your review. Without a job and a stop point, the Bot will improvise on the shared machine.
What you will learn
- Check the plan and install the right app
- Create a Bot with one job and a no-production rule
- Write a five-part handoff
- Take over the login in Agent Computer
- Turn a stable format into a skill or routine
Before you start
- SuperGrok Plus/Heavy or Cursor Pro+, Ultra or Teams
- macOS, Windows or iOS (no Linux desktop yet)
- A real task with a deliverable you can look at
Steps 1
Check the plan and install the app
You need SuperGrok Plus/Heavy or Cursor Pro+/Ultra/Teams. Open cursor.com/bot/onboarding, install Grok Bot on macOS or Windows, and sign in with Cursor. iOS exists; a Linux desktop app does not.
What you should see: The desktop app open, not grok.com. Your Cursor account signed in.
Steps 2
Create a Bot with one job
In Meet a future teammate pick a template or Create your own. Name, one job, how it should work. Example: «Never change production; separate evidence from hypotheses; lead with impact.» A catch-all Bot learns worse.
What you should see: Bot profile with a one-sentence job, not a ten-role list.
Steps 3
Write the handoff in five parts
Outcome, sources, limits, deliverable and when to stop for you. Five-minute test with no logins: attach a PDF and ask for five bullets plus dates, decisions and open questions, citing the section. Do not change the source file.
What you should see: Your message with the five parts and a PDF attached. The Bot has not asked for a login yet.
Steps 4
If it needs a login, take over the computer
Open Agent Computer, sign in (password, 2FA, CAPTCHA) and return control. The session stays on the account machine so other bots can reuse it. Do not paste secrets in chat.
What you should see: You at the Agent Computer keyboard, Bot paused, no passwords in the thread.
Steps 5
Turn a stable format into a routine
State the preference: «Five bullets, inline links, a Decisions needed section.» When the path repeats twice the same way, ask for a skill or routine. That is when it stops being a chat.
What you should see: A saved skill/routine with the same format you just approved.
Real use cases
Pipeline brief
The Bot enters the CRM, skips what is already in sequence and leaves drafts for you to approve.
Incident
Observability + screenshots + «do not touch production». Impact first.
Internal PDF
No logins. Five bullets, dates, decisions. It does not rewrite the original.
Common mistakes
A Bot that does everything
Context thins out. One job per Bot.
Passwords in chat
Login happens in Agent Computer, with you at the keyboard.
No review point
If you do not say when to stop, the Bot keeps going.
Close
When the handoff becomes a routine, you stop chatting with an AI and start having a teammate with memory. Grok the chat stays on grok.com. Do not mix them.
Next steps
- Run the same job twice and save the routine.
- A second Bot only if the job is different.
- If you want the agent on your machine, continue with Hermes.
Free guide
Want the 15-tools guide?
We send it free. We will also ping you when the next guide in this path goes out.
Unsubscribe whenever you want. We do not sell the list.
Part of the path Build with agents