Skip to content

First Bot: Create It, Assign a Task, and Watch It Work on a Cloud Computer ​

In the previous lesson, when the app was installed and you logged in successfully, Grok Bot had already automatically created your first Bot — named Grok Bot. So the first step of "Grok Bot creating a Bot" has actually been done for you. What this lesson does is turn it into a teammate that really works: define its responsibilities, assign its first task, and then go to the cloud computer to see how it actually runs.

The whole process takes about 10 minutes, and the first result, per the official claim, can be obtained in 5 minutes.

What You'll Be Able to Do After This Lesson ​

  • Understand the first Bot automatically created after login, and rename it to something that reflects its responsibilities
  • Send the Bot its first "responsibility message": one main responsibility + clear boundaries + a request to remember
  • Master the manual entry point for creating a Grok Bot: sidebar + → Create a Bot, or Cmd/Ctrl+N
  • Assign the first task with a clear endpoint — attach a document and get a result in 5 minutes
  • Watch it work on the cloud computer in the computer preview on the right, and know that closing the lid or the app doesn't affect it

Your Current Dilemma ​

  • You've installed it and seen that Bot called Grok Bot, but you don't know what to say first, and you're afraid of using it like an ordinary chatbot
  • You've heard it has a "cloud computer," but you don't know where to watch it work, or whether your own computer needs to stay on
  • You're a bit uneasy: sending emails, deleting files, clicking around random websites — will it ask me first before doing these?

When to Use This Technique ​

When you need to:

  • Go from "installed" to "actually using it": assign the first Bot a real task and run through the full workflow
  • Watch the Bot actually operate on the cloud computer, and confirm it's reliable before letting go
  • Create different Bots for different kinds of work, so each one's context is reusable

And you don't want to:

  • Throw everything at one "do-it-all" Bot — the more scattered its responsibilities, the less usable its context
  • Jump straight into scheduled automation — first run a task successfully end to end, then talk about skills and routines (those are covered in 3.2 Skills and Teaching and 3.3 Routines)

🎒 Preparation Before Starting ​

  • Installed and logged into the Grok Bot desktop app, and have seen the automatically created first Bot (1.3 Installation)
  • Issues with login or startup getting stuck have been resolved — if you still have problems, first check 1.4 Startup Troubleshooting
  • Have a document ready to use as a task (PDF, Word, or plain text all work); in step 4 you'll use it to get your first result in 5 minutes
  • Know that the cloud computer takes a few minutes to set up the first time: seeing Setting up your Grok Bot… is normal — keep the app open and wait for it to finish

Core Idea ​

Grok Bot's logic for creating a Bot comes down to one sentence: one Bot, one responsibility, one message to make it clear, and the work runs on a cloud computer.

Three things to understand first:

  1. You don't need to create the first Bot. After login, Grok Bot automatically creates a Bot named Grok Bot and opens the chat. Later, when you want to divide up work, use the sidebar + → Create a Bot (or Cmd/Ctrl+N) to create new ones.
  2. Setting up a Bot = sending one message, not filling out a bunch of forms. State the responsibilities, sources, and boundaries clearly in the first message, and ask it to remember them. The Bot decides for itself when to store things in memory; if you want to make sure it remembers, just say "please remember."
  3. The work doesn't run on your computer. Bot works on a persistent cloud computer — with a browser, terminal, and file system; files, logins, and browser sessions persist across tasks. Your app is just the window for assigning work, watching it, and approving.
Your ComputerBot's Cloud Computer
What RunsGrok Bot app: chat, watching work, approvalsBot's actual work: browser, terminal, file system
What Happens If You Shut DownApp closed, lid shut — no problemCloud work continues as usual; come back and check the results
Who uses itYouShared by all Bots under your account; each Bot has its own screen
How it relates to others—Each user gets one dedicated computer, isolated at the hardware level

💡 The cloud computer is shared within your account

This computer is assigned to your account, not to a specific Bot: cookies, files, and command-line credentials are shared by all Bots under the account, so one Bot can pick up where another left off. So—if there's something other Bots shouldn't touch, don't put it there. Multiple Bots can work in parallel, with each Bot running one computer-use task at a time on its own screen.

Follow along with me ​

Step 1: Meet the first Bot that was created automatically (no need to create one manually) ​

Why: Many people go hunting everywhere for a "Create Bot" button at this step and can't find it—because it's already been created. After you log in and click through a brief introduction, Grok Bot creates your first Bot, named Grok Bot, and opens a chat with it.

Take a look at the sidebar and the chat window. Want it to live up to its name? Click the Bot name at the top of the chat to open details, then click the name to edit it, and change it to a role-based name (for example, "Research Assistant").

You should see: One Bot in the sidebar, a chat window with it already open, and a text input box at the bottom where you can type.

  • I found the first Bot and know the rename entry point is the name at the top of the chat

Step 2: Send the Bot its first role message (define its position) ​

Why: The context accumulated by a focused Bot is far more useful than that of a jack-of-all-trades Bot. The official recommendation is to name Bots after their work—like Talent Scout, Expense Manager—the responsibility itself serves as guidance for the Bot, and it also makes the saved context reusable.

Send the first role message in the input box, covering four things: responsibility, sources, working style, boundaries, and finally ask it to remember. Template:

Your responsibility is [one domain]. Use [tools/sources] to do [specific work]. Working style: [your preferences, such as conclusions first, distinguishing facts from assumptions]. Boundaries: [what it must not do, such as not sending messages externally without permission]. Please remember this and work accordingly from now on.

Official example (a performance-investigation role, in essence: the responsibility is investigating product performance, using observability tools to look into issues, keeping links and screenshots, distinguishing evidence from assumptions, leading with the highest-impact issues, never changing production settings, and instructing it to remember):

Your job is product performance. Investigate product-performance questions with our observability tools. Preserve links and screenshots, separate evidence from hypotheses, and lead with the highest-impact issue. Never change production settings. Remember this for future work.

You should see: The Bot replies confirming its responsibility. It decides for itself what to store in memory and often mentions in its reply what it saved (but not every time); to make sure something is remembered, just say "please remember".

  • The Bot restated its responsibility and boundaries

💡 Memory is something you can talk about

What the Bot remembers, how to correct it, and how to make it forget are covered in detail in 2.4 Memory mechanisms.

Step 3: Grok Bot's manual entry point for creating Bots: sidebar + → Create a Bot ​

Why: When another piece of work has its own independent responsibility, tools, or schedule, create a separate Bot so each one's context is reusable. The official criteria (meeting any one makes it worth creating a separate Bot): independent goals or domain, independent tools and sources, a different working style, different approval boundaries, or a recurring schedule.

How to do it:

  1. Click + (New Bot) at the top of the sidebar, or press Cmd/Ctrl+N. On team accounts, + opens a menu—choose Create a Bot
  2. In Create New Bot, give it a name, pick a shape and color for its avatar, and click Create
  3. Once the chat opens, send a role message first just like in step 2, then assign work

You should see: The new Bot appears in the sidebar, with its chat window open.

  • At least two Bots in the sidebar, each with different responsibilities

💡 primary Bot: your main point of contact

If you don't have a primary Bot yet, the app will show Introducing your primary Bot: choose Create primary Bot to create a new one, or Choose an existing Bot to pick one from your existing Bots and then Confirm. The primary Bot will proactively reach out to align with you and coordinate the work of other Bots. To switch it: right-click it in the sidebar and choose Replace with different Bot (a Team Bot cannot serve as the primary Bot).

Step 4: Assign the first task: results in 5 minutes ​

Why: For your first task, pick something small but real, to run through the whole "assign → work → deliver" flow. The official starter task that produces results in 5 minutes: attach a document and have the Bot summarize it.

Send it the document as an attachment, or paste the content directly into the input box, then send:

Summarize this document into 5 key points. List all dates, decisions, and unresolved issues in a separate section, noting the source chapter for each item. Do not modify the source file.

Official original text (in English):

Summarize this document in five bullets. List every date, decision, and open question in a separate section, and cite the section for each item. Don't change the source file.

You can apply this formula to all future task assignments—a strong request = outcome + relevant sources + constraints + deliverable + where to stop. For example, "just organize it into a table, don't send it out yet".

Don't feel like typing? On desktop, click Start voice input or press Cmd/Ctrl+D to dictate; when the input box is empty, you can also choose Start voice chat to just start talking.

You should see: The Bot starts working and reports progress in the chat; a few minutes later it delivers 5 key points, plus a separate section with dates, decisions, and the list of issues, with the source file untouched.

  • I got my first result, and the source file was not touched

💡 Attachment limits

On desktop, each message allows up to 20 attachments; documents and other files are limited to 250 MB each (images 25 MB each, videos 1 GB each). When a single file exceeds the limit, the composer will flag it as too large and exclude it. For the full limits table, see 2.2 Files and reviewable results.

Step 5: Watch it work on the cloud computer (computer preview) ​

Why: The Bot's work runs on the cloud computer, not on your computer. Watching it operate firsthand is the fastest way to build trust.

Click computer preview in the panel on the right side of the conversation to open the cloud computer screen.

You should see: A real computer—with the Bot clicking, typing, and navigating on it, and its current state updating in real time.

Three key facts:

  • You can leave at any time: close the preview and the work keeps running

  • You can close the app or shut the lid: cloud work continues, come back later to see the results

  • The first time requires setup: Seeing Setting up your Grok Bot… is normal; it takes a few minutes, so keep the app open

  • I saw the Bot's actual operations in the computer preview

Step 6: Handling approval cards and Take over (the key to letting go) ​

Why: Auto Review is on by default—every action the Bot wants to take goes through review first, and most are approved automatically; when it needs your nod, an approval card appears in the chat stating what it wants to do and what the parameters are. This is the safety net that lets you "dare to let it act."

When you see an approval card, there are three buttons:

ButtonEffect
Allow onceAllow this time without saving a rule
Always allowAllow, and save similar actions into Custom Rules so they pass automatically next time
DenyDeny; it won't retry this action until you send another message

Some cards carry warnings (for example, This can't be undone)—read carefully before clicking. Approval cards for work you initiated in the chat will wait for you indefinitely and never time out.

Sensitive steps get handed to you: SSO, passkeys, CAPTCHAs it can't get past, confirmations on other devices, QR codes, bank card verification, websites that explicitly require a real human—forms can't handle these, so the Bot hands the computer over to you. Click Take over to take control, do only the step it got stuck on, then click I'm done to hand it back and let it continue.

You should see: after approval the Bot keeps working; after you take over, finish, and click I'm done, the Bot resumes its work.

  • I can clearly explain the difference between the three approval card buttons, and I know Take over only handles the step it got stuck on

⚠️ Never paste passwords into the chat box

The official guidance is explicit: do not paste passwords or one-time verification codes into ordinary chat. When the Bot needs to log in, it first uses logins stored in Vault, then a connected password manager, and then asks you via Secure Form—the value goes straight into the page, invisible to the Bot. API keys go through a masked secure secret card.

Checkpoint ✅ ​

  • I know the first Bot is created automatically; to create new ones use the sidebar + → Create a Bot or Cmd/Ctrl+N
  • My Bot has one clear responsibility, and I asked it to remember it
  • The first task has been delivered (that summary with 5 bullet points)
  • I've watched it work in the computer preview, and I know closing the lid or quitting the app has no effect
  • I can handle approval cards (Allow once / Always allow / Deny) and Take over → I'm done

Pitfall reminders ​

❌ Making your first message "Hello, what can you do?" ​

Treating it as a chatbot is a waste. Your first message should directly give responsibility + boundaries + "please remember." A Bot with a clear responsibility (like a Talent Scout or Expense Manager) has reusable saved context; a General Helper offers no guidance and its context is hard to reuse.

❌ Pasting passwords or verification codes into the chat box ​

Official rule: never put passwords or one-time verification codes into ordinary chat. When the Bot needs to log in, it first checks Vault, then a connected password manager, then asks you via Secure Form—the value you enter goes straight into the page and the Bot never sees it. For steps forms can't handle, like SSO or CAPTCHAs, use Take over to do that step yourself, then click I'm done.

❌ Assuming quitting the app / closing the lid interrupts tasks, or that your own computer must stay on ​

Neither is needed. The work runs on a cloud computer: quit the app, close the lid, and the cloud keeps going; your computer is just a remote control, and the Bot's work doesn't occupy your machine.

❌ Repeatedly restarting the app during the cloud computer's first-time setup ​

First-time setup or updates may take a few minutes, during which Setting up your Grok Bot… is displayed. Keeping the app open and letting the progress finish is the correct move; if the progress stays stuck for a long time, check Error Quick Reference and follow it.

Advanced tips (optional) ​

Steering and emergency stop: While the Bot is working, just send a new message—your message takes priority over background work and can steer it; to stop immediately, say "Stop now" (note: already-completed actions are not undone).

Website won't open? When the Bot times out or gets blocked browsing certain websites, the official fix is to route its traffic through your computer: Settings → Computer → Route traffic through this computer. See 5.3 Traffic Routing and Local Execution for details.

Solidify what runs reliably: Once a workflow is stable, save it as a skill (invoke with @name next time) or a routine (runs automatically on a schedule or event trigger)—see 3.2 Skills and Teaching, 3.3 Routines.

Multiple Bots in parallel: Each Bot has its own screen on the shared cloud computer and can work simultaneously and hand off to one another—see 3.5 Multi-Bot Collaboration.

Lesson summary ​

✅ Grok Bot's two paths for creating a Bot both work now: the first is created automatically after login (named Grok Bot), and afterwards use the sidebar + → Create a Bot or Cmd/Ctrl+N.

✅ The core action for creating a Bot is the first responsibility message: responsibility + sources + way of working + boundaries + "please remember."

✅ The first task has been delivered: with attached documents, 5 bullet points, and a separate section for dates/decisions/questions, leaving source files untouched.

✅ You've watched it work on the cloud computer in the computer preview—closing the lid or quitting the app has no effect, and users are hardware-level isolated from one another.

✅ You can use the three approval card buttons (Allow once / Always allow / Deny) and Take over → I'm done.

Key information recap:

ItemKey points
First BotCreated automatically after login, named Grok Bot; to rename, click the name at the top of the chat
Manual creationSidebar + → Create a Bot, or Cmd/Ctrl+N
Responsibility messageResponsibility + sources + way of working + boundaries + ask it to remember
Strong request formulaOutcome + sources + constraints + deliverable + where to stop
Watching it workThe computer preview panel on the right side of the conversation; closing the lid or quitting the app doesn't stop it
ApprovalsAuto Review on by default; Allow once / Always allow / Deny
Sensitive stepsTake over → do only that one step → I'm done

Next lesson preview ​

The desktop side is up and running; in the next lesson we'll put it on your phone: Mobile: iPhone/Android installation and dispatching tasks anytime.

You will learn:

  • Installing and logging in to the mobile app (iOS 18+ / Android 9+), same account, same Bots, same cloud computer
  • Siri and Shortcuts: dispatch tasks just by speaking
  • Watch it work and approve requests on your commute

More details about everyday conversations (attachments, dictation, voice chat) are in 2.1 Messages and Conversations; to make approvals even easier, continue with 3.1 Approvals and Auto Review.

gaodong.aiAboutPrivacyContact

Independent tutorials, not affiliated with any product mentioned. Product names and trademarks belong to their owners. Check official pages for prices and policies.