Skip to content
Start setup
An office scene from the official Grok Bot launch film
Grok Bot Field Guide / Independent resourcePersonal life & business operations

A named Bot team you can install.

So follow-through is written down, not stuck in one person’s head. Start from a full questionnaire, a hobby team, or one mission skill. Grok Bot is a separate desktop app; this site only builds the files. No account. Answers stay in this tab.

Paid installationWant this installed for you?See pricing

Leave with
a named Bot team.

These two questionnaires build a ZIP in your browser. You install those files in the Grok Bot desktop app — named Bots, written jobs, a first task you can check. Blueprint, Method and the earlier intake quiz are examples or older tools.

  1. Name the help you need Pick personal or business, then the areas you want help with. Skip anything that does not apply.
  2. Download a setup ZIP This site builds the files in your browser. The file is named grok-bot-personal-setup.zip or grok-bot-business-setup.zip. No account. Answers stay in this tab.
  3. Install, then check one task Create each Bot in the desktop app, paste its description, attach its reference file, then run one small task you can check.

Your answers stay in this tab. Save a draft if you want to come back. No account is required to generate files.

Read the operator manual ↗

Start from a hobby,
not a blank week.

Each kit is the smallest team that can run that interest: two named Bots, two jobs, a first task you can check. Split when the words differ. Add a third Bot only when you catch yourself correcting context.

More kits in the catalog, including growing, learning, family logistics and bills. Starter files, not live Bots.

See every interest team ↗

Give one Bot
a job it can finish.

A mission is a focused skill: inputs, steps, done-when, stop-when. Start with one task. Save a skill after you accept the trial. Add a routine only after that.

Also purchase research and a community interview brief. Copy the skill or download a one-Bot ZIP.

See every mission ↗

Act on what
is current.

Grok Bot changes fast. Read sourced notes here instead of trusting last month’s memory. Every fact keeps its source and the date we checked it.

—records in the library
—documented practices
—sources in the registry
Product timeline

    Tell each Bot
    what it can do.

    So a test cannot quietly open sites, change files, or use connected accounts you did not mean to share. Set those rules before you connect anything.

    01

    A test can take real actions

    A test can open websites, change files, and use connected tools. Start with a small task you can check.

    02

    Your Bots share one computer

    Your Bots can share files, browser logins, and connected accounts. A Bot name does not keep those things private from your other Bots.

    03

    Read before you approve

    An approval lets the Bot do the action it shows you. Read the action before you say yes.

    Check the supporting records

    Run it without
    guessing.

    The manual, an example roster, and sourced records — so you can operate the team and check a claim without relying on stale chat memory.