Another new learning this week!

I did not need another chat window that forgot everything by Tuesday.

I needed roles. Someone to triage. Someone to draft. Someone to check before anything went live. Someone with one job, every day.

That is how I got started with Grok Bot.

1) What Grok Bot is

Grok Bot is an xAI product for persistent AI teammates.

You create named bots. You message them like coworkers. You give them a job and tool access. They work on a cloud computer (browser, files, terminal, connectors). Closing your laptop does not stop the work.

That last part is the unlock.

It is not Grok chat. It is not Grok Build (the coding CLI).

Different products. Different setup. Do not mix the docs.

Official product page: https://x.ai/bot

2) How it compares (Grok Bot, OpenClaw, Hermes, Muse)

Caption: Four ways to run always-on AI help. Different jobs. Many people will run more than one.

Grok Bot

OpenClaw

Hermes

Muse (Meta)

What it is

Named AI teammates on a managed cloud PC

Open-source always-on assistant you host

Open-source persistent agent + skills loop

Consumer personal agent for life admin

Who runs it

xAI cloud (shared per account)

Your machine(s) or VPS

Your machine(s) (optional hosted)

Meta Secure VM per user

Best first use

Work teammates and multi-bot ops

Own the stack and your data

Long-running agent with memory/skills

Email, travel, shopping via apps / WhatsApp

What's unique

Role roster + routines; bots keep working offline

Free / open / BYO models; many chat channels

Self-improving skills + open toolkit

Mass-market UX; approvals + audit for sensitive acts

Quick takeaways

  • Want a team of work bots with roles → Grok Bot

  • Want to host and own the stack → OpenClaw or Hermes

  • Want a consumer life agent → Muse

My take after using both (Grok Bot vs Muse)

This is not a lab scorecard. It is what I am seeing in real use.

Grok Bot feels stronger when you want to plug into lots of tools outside one ecosystem. Connectors, apps, browser work, and a roster of named bots. You can organize work as a small team: one bot for newsletter, one for podcast, one for LinkedIn drafts, with slightly deeper specialization on each.

Muse feels strongest inside the Meta world: Instagram, Facebook, and email are where it shines. Outside that, the connector / app surface feels more limited right now. The mental model is also different: one agent running many jobs, not a tree of specialists.

So the simple split I use:

  • Need a fleet with roles and broader tool reach → Grok Bot

  • Need a personal agent that is great on Meta apps + everyday life admin → Muse

I can run both. I do not treat them as twins.

3) How to access it

You need an eligible plan, then the app.

Included with Cursor

  • Every paid individual Cursor plan (Pro, Pro+, Ultra)

  • Cursor Teams (self-serve)

Sign into Grok Bot with the same Cursor account.

Or link SuperGrok / X Premium+

  • Individual SuperGrok, SuperGrok Plus, SuperGrok Heavy, or X Premium+

  • Link from the Grok Bot plan screen

  • Linking is a usage grant, not a second Cursor plan

  • Cursor plan + SuperGrok link do not stack extra Grok Bot usage

Sources: cursor.com/help/grok-bot/plans · cursor.com/help/grok-bot/supergrok · docs.x.ai/grok-bot/get-started

Do: confirm access before you install five times. Don't: mix Grok chat login with Grok Bot setup.

4) How to purchase / subscribe

There is no separate "Grok Bot only" SKU in the public plan docs. You buy access through Cursor or SuperGrok / X Premium+.

Path A: Cursor (Grok Bot included)

  • Pro: $20/mo

  • Pro Plus: $60/mo

  • Ultra: $200/mo

  • Teams: $40/seat/mo

Path B: SuperGrok, then link

  • SuperGrok: $30/mo

  • SuperGrok Plus: $100/mo
    Then link inside Grok Bot.

Included usage resets weekly. Extra can continue as on-demand through Cursor if enabled. If a live page price differs, trust the live page.

5) How I actually built the motion (The First 1% tree)

I stopped collecting random bots. I built a tree.

Caption: Dr Eggbot births bots. Chief of Staff is the hub. The One owns The First 1% lane. Podcast, newsletter, and marketing split on purpose. SecCheck sits before live actions.

Read the tree top to bottom

  1. Dr Eggbot (bot factory)
    Download this first. It designs focused bots so you do not invent vague "assistants" from scratch.
    Lauren Tan (@poteto) built it.
    Add: https://x.ai/bot/marketplace/bots/dr-eggbot-v2 · https://bot.store/bots/dr-eggbot

  2. Chief of Staff (hub)
    Triage. Prioritize. Brief. Route. The CoS does not own every craft job. It pulls the right desk.

  3. The One (First 1% lane lead)
    Owns this brand lane end to end: newsletter, podcast, and the marketing motion around them.

  4. Separation inside the lane

    • Podcast: Podcast buddy

    • Newsletter: 1% Blog (this desk)

    • Marketing / social drafts: Content Desk, LI Desk, X Ideas (inspiration only, never auto-post)

    • Creative / video: Video Edit Desk

    • Safety gate: SecCheck (before live actions)

Why separate podcast vs marketing vs creative?
Different jobs. Different voice. Different risk. A podcast outline should not silently become a LinkedIn post without a human yes. A rough cut should not publish itself.

Standing rule under the whole tree: sample first. My yes before anything goes live.

6) Step-by-step: get started tonight

  1. Confirm eligible access (Cursor paid plan, or SuperGrok / X Premium+ ready to link).

  2. Download the app from https://x.ai/bot

  3. Sign in with your Cursor account. Link SuperGrok if that is your path.

  4. Download Dr Eggbot first. (See GIF below)

  5. Tell Dr Eggbot one painful job in one sentence. Let it create that specialist.

  6. Give the new bot a real first task (outcome, sources, constraints, deliverable, when to stop).

  7. Watch the computer view. Approve sensitive steps yourself.

  8. Write three notes: worked / burned usage / try next.

  9. Only then add a hub (Chief of Staff) and more desks.

Do: start with Dr Eggbot · one job per bot · sample before publish · connect only tools that job needs

Don't: spin up a fleet on night one · treat each bot as an isolated secure computer · mix Grok Bot docs with Grok chat / Grok Build · auto-publish anything

7) Standing rules

  1. Sample first.

  2. My yes before publish.

  3. SecCheck before consequential moves.

  4. Brand lanes stay separate. This issue is The First 1% only.

Closing

Getting started with Grok Bot is not about collecting agents.

It is about designing a motion: factory, hub, lane lead, desks, approval.

Start with one painful job. Let Dr Eggbot birth the specialist. Promote a Chief of Staff when the sidebar gets loud. Grow the tree only when the last branch is actually running.

If you install this week, reply with the step that slowed you down. I will shape the next setup guide around that exact friction.

Keep building,
Jon
The First 1%

Keep Reading

View more
caret-right
© 2026 The First 1%.
beehiivPowered by beehiiv