Grok Bot: second teammate (2026)

If you finished grok-bot-primer-teammate, you already have a Bot with a plan, desktop app, five-part handoff, logins in Agent Computer and a routine or skill. This flow adds a second Bot with a different job — not «CRM + code + long-form writing» on one profile. Grok Bot is not grok.com; official onboarding is at https://cursor.com/bot/onboarding. Multiple bots on one account share the Agent Computer.

1. Steps 1

   Confirm Bot #1 still holds

   Before creating anything new, open the Grok Bot app (not grok.com) and run the same job that already worked: a saved routine or a short test handoff. Success = the Bot delivers the expected format and stops where you said («wait for my OK»). If it fails, fix Bot #1 first — a second Bot does not repair a broken first flow.

   What you should see: A reply with Bot #1's usual deliverable. Agent Computer active only for that job, with no plan or app errors.

2. Steps 2

   Pick a one-sentence job — different from Bot #1

   Write Bot #1's sentence in a notes doc («summarize internal PDFs in five bullets») and Bot #2's in another register. Examples that fit: Bot #1 = weekly research briefs; Bot #2 = inbox triage with drafts for approval. Or Bot #1 = incident notes; Bot #2 = vendor comparison PDFs. What does not fit: one Bot doing CRM, code and long writing. If the new job is only «another tone» for the same work, extend Bot #1's instructions instead of creating #2.

   What you should see: Two job sentences in a notes doc. Each with a distinct deliverable and format, no overlap.

3. Steps 3

   Create Bot #2 with its own name and instructions

   In the app, create a new Bot. Name it for the job («Inbox-Triage» vs «Research-Brief»). In instructions: the one-sentence job, delivery format, what not to touch (production, sends, deletes) and «stop and wait for my OK before acting outside scope». Do not paste Bot #1's full block — reuse safety rules only if they are identical. Confirm the account is still eligible (SuperGrok Plus/Heavy or Cursor Pro+/Ultra/Teams).

   What you should see: A second profile in the Bot list with instructions that mention one job and no-send / no-production rules.

4. Steps 4

   Clean the shared Agent Computer

   Multiple bots share the same cloud machine. Before Bot #2's first handoff: close sessions and tabs Bot #1 left open, clear temporary downloads if any and check no active login remains that #2 could misread. Never paste passwords, tokens or 2FA codes in any Bot chat — you do logins in Agent Computer, at the keyboard.

   What you should see: Agent Computer with a clean desktop or only the apps job #2 needs. No CRM tabs from Bot #1 still open.

5. Steps 5

   Bot #2's first handoff with no login

   Start with a test that needs no credentials: an internal PDF, notes in a doc or a public link. Use the same five-part scheme from the first flow: context, deliverable, format, limits, stop point. Example: «Read this product notes PDF. Return three bullets: decision, deadline, risk. Do not rewrite the original. Stop here and wait for my OK.» Review the result like a PR before you approve.

   What you should see: Three bullets grounded in the PDF, no invented prose. The Bot says it is waiting for your OK and does not open apps that need login.

6. Steps 6

   Second handoff: login you take in Agent Computer

   Once the no-login test passes, pick a job that needs a signed-in app — for example reading tickets in a dashboard or a shared mailbox. In the handoff say which app to open, what to read and what not to do (no send, no delete). When the Bot needs access, you enter Agent Computer: username, password, 2FA, CAPTCHA. Do not dictate secrets in chat. After login, let the Bot collect; review the draft before any send.

   What you should see: You in Agent Computer completing login. Bot #2 produces a draft or summary and stops at the review point.

7. Steps 7

   Routines and skills only for this Bot

   If handoff #2's format repeats, save it as a skill or routine on Bot #2's profile — do not copy Bot #1's routine and rename it. Each Bot carries its own routines: research should not trigger inbox triage. Before you automate, run the same job twice manually and confirm the deliverable is stable.

   What you should see: A new routine or skill under Bot #2 named for job #2. Bot #1 keeps its routines unchanged.

8. Steps 8

   One Bot or two? When to stop

   Stay on one Bot if the «second job» is the same deliverable in another tone or the same tool with another folder. A second Bot is worth it when the output format changes (bullets vs email drafts), the main tool changes (CRM vs ticket panel) or the risk changes (read-only vs drafts that could send). If you need a third very different job, consider Hermes on your machine or Cursor for code — do not stack five Bots on the same VM without hygiene.

   What you should see: A written decision: «two Bots are enough» or «I extend #1's instructions». No third profile created on impulse.