Tutorials

How to use Grok Bot: your first task, step by step

Understand Grok Bot access, create a focused Bot, connect its tools, and define a small first task with a result you can check.

Official Grok Bot product image: AI teammates you can hand real work to
Based on official documentation

Grok Bot gives an AI assistant access to a persistent cloud computer and connected tools. A useful first session begins with one small job, not a long list of everything you hope to automate.

This guide explains the setup path described in the official documentation. It is not a hands-on installation review.

Check access before installing

Use the download link on the official Grok Bot page. The app's sign-in flow checks account access; eligible legacy subscribers may need to link their subscription. Our plan explainer covers the current distinction between new and legacy plans.

Before connecting a work account, decide which task requires it. A first experiment using an uploaded, non-sensitive document is easier to inspect than a task that immediately spans your inbox, calendar, and customer database.

Give one Bot a focused job

After setup, define a role with an outcome, a source, and a boundary. For example:

You are my research organizer. Turn the material I provide into a short, source-linked brief. Separate direct evidence from your suggestions. Ask when an important input is missing. Keep this as your ongoing role.

Avoid a vague role such as “manage my business.” It gives you little basis for checking whether the result is useful.

Run a task you can verify

Choose a short document whose contents you already understand. Try this first request:

Read this document and return five main points, every explicit deadline, and a list of unresolved questions. Link each item to the relevant section. Do not edit the original. If a date is implied rather than stated, label it as an inference.

Check the output against the input. Did it preserve the dates? Did it invent a decision? Is the result concise enough to use? Your corrections become a better role definition.

Connect tools only as needed

When a task requires a service, follow the app connection or secure sign-in flow. Keep credentials out of ordinary chat. For an early inbox experiment, limit the request to preparing a small review list rather than sending messages.

Decide what to automate next

Run the same kind of task with a second input. If it works without extensive corrections, describe the method as a reusable process. Then move on to skills and routines. A useful finish line is a result you can verify, not simply a Bot that says it is done.