Grok chat
The friend on the phone
You type. It answers. Perfect for ideas and “explain this to me.” You still do the cooking.
Lesson 00 · Start here
You’ve already used half of AI. This is the other half — and it feels different.
You ask. It answers. That part you know. This course is about helpers that can get up from the table and actually do the work.
Picture this
Chat is a brilliant friend on the phone. They can tell you, step by step, how to make lasagna. Then they hang up. You still buy the noodles.
An agent is a cook. Same knowledge. Hands. They taste the sauce. If it needs salt, they add salt. They don’t read you the recipe and leave.
You might be thinking, “So it’s just a fancier chat?” Fair. Keep going. The difference is not smarter talk. It is who is standing at the stove. If you’d rather hear the pictures: tap Teacher voice up top, or Listen on any gold story.
Grok Bot
A cook in their own kitchen
You text the order from the couch. They have their own stove, their own keys to your apps. Close the laptop — they keep cooking.
Grok Build
A cook at YOUR stove
They stand in your kitchen — the folder of files on your computer. You watch them chop. You taste before anything goes in the oven.
When you walk out, you can
- Tell a friend the phone-vs-cook difference in one breath
- Say why a cook beats a cookbook, even if the book is a masterpiece
- Pick the phone, Bot, or Build for a real job
- Hand off work the way you’d brief a new hire — clearly, with a stop line
About 40 minutes · no computer skills needed
We’ll play little scenes, pause for a check, and send you out with a first job you can copy. If you don’t keep a “kitchen” of files on your computer, skip Build’s install. Remember the picture anyway.
Grok Bot is new (a test version, as of August 2026). We’ll keep using kitchen words on purpose.
Before we cook — a tiny check-in
That leftover cooking is the whole point. Chat is a genius on the phone. Helpers that can act are built to finish dinner.
Lesson 01 · The world you know
Chat is a genius on the phone. The stove is still yours.
Grok in a tab or the Grok app is chat. You type. It replies. Sometimes it looks something up or draws a picture. The answer still lives in the box. You carry it into the real world — like hanging up and going to the store.
When you want the phone
- “Explain this like I’m new.”
- “Give me three ways to say this.”
- “Talk me through a decision.”
- A first draft you’ll paste somewhere
The quiet deal
Grok, ChatGPT, Claude — same deal. They talk. You walk. Words in a box. Hands on your side of the table.
That is not a flaw
You don’t need a cook to discuss the menu. Chat is the right tool for thinking. The trouble starts when the job is “please make dinner,” not “what’s for dinner?”
Watch a perfectly normal chat
Press play. This is a good chat. Maya gets a real outline. Then notice who still has to cook.
Grok chat · the phone
The recipe was excellent. Dinner is not on the table. Maya still opens email, finds the numbers, fills the outline, hits send. Chat got her to “almost.” Cooks exist for the rest.
Lesson 02 · The leftover work
You have been the waiter between the cookbook and the stove.
Take the question to the phone. Bring the recipe back. Carry the plate. When the sauce is wrong, walk it back again. Three little trips. They add up.
The restaurant at rush hour
Chat is the cookbook in the office. A cook is at the stove. You have been running the hallway between them. An agent is what happens when the cookbook grows arms and walks into the kitchen.
Trip 1 · Take it in
You retype the email, the spreadsheet, the “here’s what happened” so the AI can see anything at all.
Trip 2 · Bring it out
You carry the reply into Gmail, a document, a website, a list — and make it real with your own hands.
Trip 3 · Walk it back
The number is wrong. The page looks different. Something breaks. Back down the hallway you go.
Same dinner, two kitchens
The job: Change the big title on a website, make sure it still works, save it. Step through. Count how many times you have to move.
Phone path · you run the hallway
Cook path · they stand at the stove
Your trips with chat: 0
Your trips with a cook: 0
Same brain. Different body. A smarter cookbook still cannot stir. The cook can be average and still beat it at dinner — because dinner happens in the pot.
Lesson 03 · How a cook actually works
Stir. Taste. Add salt. Taste again. That circle is the whole secret.
People call this agentic AI. Fancy word. Plain meaning: not a speech. A shift at the stove. Chat is one reply. An agent keeps going until dinner is done, they’re stuck, or they need the head chef — that’s you.
Click the four steps. This is the same loop a person uses when they cook, drive, or pack a suitcase. Do. Look. Decide. Repeat.
Another picture, if the kitchen is tired
Chat is asking a brilliant librarian which books exist. An agent is a research helper who can pull the books, notice a missing chapter, and bring you a one-page brief — then ask before they publish it.
You are still the head chef
A good cook does not “go wild.” They stop for the keys, the credit card, sending the plate out, throwing food away, or anything customers will eat. Power with no taste-test is just a faster mess.
Lesson 04 · Why a cook beats a cookbook
The leap is not a better recipe. It is dinner actually landing on the table.
If chat already feels like magic, a cook can feel like “the same thing, plus extra steps.” It isn’t. A masterpiece on paper and a plate in front of a guest are different kinds of done.
The 90 / 10 problem
Most AI gets you almost there — the dish is 90% plated. You still have to walk it to the table. That last stretch is where jobs live or die. A cook finishes because the food lands where a person would put it.
Chat, on a typical jobstuck at “almost”
A cook, same jobon the table
Open these. They’re the same idea from six angles. If you remember only one: the cook can taste.
1. They can taste their own food
Chat says “add a pinch.” A cook adds it, tastes, and tries again. That’s why they’re dependable — not because they sound sure.
2. They look in the fridge, not at your grocery list
You will always forget an ingredient. A cook opens the real inbox, the real website, the real folder. What’s actually there beats what you remembered to mention on the phone.
3. You stop running the hallway
The old way: something breaks → copy it → paste into chat → copy the fix → try again. A cook does that loop at the stove. You only step in for taste, risk, and “should we serve this?”
4. More than one cook
Chat is one phone call. Grok Bot can run a few named teammates overnight. Grok Build can send helpers to look around while another one chops. You become the person who tastes, not the person who stirs every pot.
5. They remember how you like the sauce
A named Grok Bot keeps notes, files, logins, and Tuesday’s repeating job. Grok Build remembers the folder it’s in and how you like things done. Next week doesn’t start from a blank recipe card.
6. Done means on the table — not described
A draft in a chat box is not a sent email, a saved file, or an updated list. Cooks work in the real apps, so “done” means done.
Lesson 05 · Grok Bot
Grok Bot is a cook with a kitchen that is not yours.
You text the order from the couch. They have their own stove, their own keys to your apps, and they keep cooking after you turn out the lights. Several of them can work at once. They can even talk to each other.
Remember the kitchen?
Chat is the phone. Bot is a teammate in a kitchen across town. You don’t have to be there. In the morning they bring you plates — drafts — and ask: serve this, or not?
What they have
- Their own computer on the internet: a browser, files, a place to type
- All of your bots share that one kitchen — and its keys
- Each bot gets their own counter, so a few can cook at once
- An app on the computer and on the iPhone — same conversation
What they do
- Finish a job in the real apps, not as a recipe in chat
- Come back when something needs your yes
- Learn a process if you show it once, then cook it later
- Remember how you like the sauce
Still a test version (as of August 2026). You need a higher-end Grok or Cursor plan. App for Mac, Windows, and iPhone.
Hire a tiny teammate. Watch them cook.
Their kitchen · across townalways on
waiting for an order…
Name a bot and hand something off. You can close the laptop. The kitchen stays open.
How people actually hire
- One cook, one job. Not “run the whole restaurant.”
- Say what dinner looks like, which fridge to open, what never to do, what to bring you, and when to wait for a taste.
- When a password or phone code is needed, you take the screen. Never text the keys.
- Correct the plate. Save the recipe. Only then put it on Tuesday’s repeating menu.
Good first orders
- Research people and leave draft emails — do not send
- Click through a problem on a practice site and take pictures
- A morning briefing of what changed
- Match receipts to a list and flag anything odd
Lesson 06 · Grok Build
Grok Build is a cook standing at YOUR stove.
If you don’t keep a kitchen of files on your computer, you can still learn the picture and skip the install. Bot is the everyday teammate. Build is for when the ingredients live in a folder on the machine in front of you.
Same cook family. Different kitchen.
Bot has a kitchen across town. Build puts on an apron in yours. They open your cupboards. They chop where you can see. They wait before the oven.
What they have
- A full-screen window on your computer (it looks a bit like an old-school text screen)
- They can see the folder you opened — that’s the cupboard
- They can read files, change them, search, look things up, keep a to-do list
- They ask “is this ok?” before they change things, unless you say otherwise
What they do
- Explain a folder by actually opening it, not guessing
- Fix a problem, taste, try again
- Write a plan first when the job is fuzzy — you say yes before they chop
- Send extra helpers to look around while they cook
How you start (when you’re ready)
You do not have to do this today. When you want to, someone computer-comfortable can walk you through it. The short version:
- Install Grok Build on your computer.
- Open the folder you want help with.
- Start Grok Build. The first time, it opens a sign-in page.
If that sounds like “not me yet,” that’s fine. Keep the picture: Build lives at your stove. Bot lives in a kitchen that is not yours.
Try a practice cupboard
This is fake. Your real files are safe. Try: what is in this folder, fix the login problem, make a plan first, or help.
Grok Build · practice folder · asks before changing things
Hi. This is a practice cupboard.
Your real files are not touched.
Type a job below. In the real kitchen you would see which files I opened and what I want to change.
Plan first
When the job is fuzzy, they look around and write a plan. You say yes, change this, or wait — before anyone chops.
Extra hands
They can send a helper to look in the cupboards, and another to cook, at the same time. Those helpers cannot hire more helpers. The kitchen stays a kitchen, not a crowd.
Saved recipes
If you cook the same dish often, you can save the steps. Next time they already know the method.
Lesson 07 · Two kitchens
Same family of cooks. Completely different kitchens.
Mixing Bot and Build up is the most common beginner mistake. Both can do things. One has a kitchen across town. One is wearing an apron at yours.
If you remember nothing else
Phone = chat. Kitchen across town = Grok Bot. Your stove = Grok Build. There is no prize for using the fanciest tool. Use the one that matches the kitchen.
What are you actually trying to do?
Tap a real-life need. We’ll point you at the phone, the kitchen across town, or your stove.
Side by side
| If you care about… | Grok Bot | Grok Build |
|---|---|---|
| Where it lives | A computer on the internet. You message it from your computer or phone. | Your computer. Inside a folder of files. |
| Easy picture | A cook in a kitchen across town | A cook at your stove, in your cupboard |
| What computer? | Its own: browser, files, logins to your apps | Yours: the files and programs already on your machine |
| When the laptop closes | Keeps working | Stops (you were using it on that laptop) |
| How you talk to it | Like texting a coworker. You can watch their screen if you want. | A full-screen window that shows what it is reading and changing |
| Best at | Jobs that hop across email, websites, spreadsheets, and customer lists | Jobs inside a folder: explain it, change it, check it still works |
| Who they are | Named bots with a job title, that stick around | You open it in a folder, do some work, and can come back later. |
| How they learn a process | Show them once, save it, put it on a schedule | You tell it the rules for that folder. It follows them next time. |
| More than one at once | Many bots. They can message each other. | Extra helpers working at the same time, then they report back |
| Overnight work | Yes — repeating jobs while you sleep | Not really. It works while you are there (or someone starts it) |
| Logging into everyday apps | Signs in like a person, even on messy websites | Uses what is already on your computer, plus extra apps you connect |
| Who it is for | Anyone who works in apps — sales, office work, support, and more | People working in a folder of files on their own computer |
| Safety | It asks before sending, paying, or deleting. You type passwords yourself. | It asks before changing files. You look at the changes first. |
| Gotcha | All your bots share one computer. A login for one is a login for all. | It can see the files in that folder. That is why it asks first. |
Text the kitchen across town when…
The work hops across websites and apps. You want a named owner. You want it cooking at 2am. You would otherwise hire a sharp intern with a laptop.
Call the cook to your stove when…
The work is a folder of files on a computer you control. You want to see every chop. You want a taste-test that it still works. You would otherwise sit next to someone and point at the cupboard.
They are teammates, not rivals. Build can help make the thing. Bot can research customers, click through a problem on the website, draft the launch email, and keep the list honest. Chat is still the right door for “talk this through with me while I think.”
Lesson 08 · How to give an order
Don’t say “help with dinner.” Say what plate you want, and when to wait.
A chat question wants a good reply. A job for a cook wants finished work you can taste. Five parts. That’s the whole beginner skill — the same way you’d brief a new hire on their first Tuesday.
The bad order vs the good one
“Can you help with dinner?” is a wish. “Make the Tuesday pasta from the recipe on the fridge. Don’t serve it. Leave it on the counter for me to taste. If you’re missing garlic, ask — don’t invent it.” That’s a job.
The five-part order
- Done looks like — what should be true when they stop?
- Which fridge — which apps, files, websites, or emails?
- Never — what must they not do?
- Bring me — what do you want to see?
- Wait for a taste — when do they pause for your yes?
Phone vs kitchen
phone “Can you help with my weekly report?”
kitchen “Make this week’s report from the attached spreadsheet and yesterday’s notes. Five bullets, links in the text, a last section called ‘Decisions needed.’ Do not email anyone. If a number is missing, ask me — don’t guess.”
Your turn. Taste these orders.
Which one can a cook actually run with?
House rules for every kitchen
- One cook, one job. Split when the work naturally splits.
- Taste, then serve — for anything that leaves the building: send, pay, publish, delete, change the live site.
- When you correct them, name the lasting preference: “This is how we plate it next time.”
- If you wouldn’t text a new hire the keys, don’t put them in the message. Take the screen instead.
Lesson 09 · First service
You’re ready. Keep the training wheels on for a week.
Don’t begin with “run the restaurant.” Begin with look-and-draft. Taste everything. Add sending and saving only after you trust the plates.
The picture, one last time
Chat is the phone. An agent is a cook: do, look, decide. Bot has a kitchen across town. Build stands at yours. You are the head chef. Taste before it leaves the pass.
Job A · Grok Bot
After you install the app and make one focused bot.
Summarize the attached document in five bullets. List every date, decision, and open question in a separate section. Note the page or section for each. Do not change the original file.
Next: compare this week’s numbers to last week’s, and change nothing. Then: draft emails, still do not send.
Job B · Grok Build
Only if you have a folder of files on your computer. Ask a computer-comfortable friend to help you install if you need to.
Explain this folder to a new teammate. What is it? How do you open it? Which three files would hurt us most if they broke? Do not change anything yet.
Next: “Fix the login problem and check that it works.” Then a small change with “show me first, do not save it for good.”
The head-chef card — keep this
- You type passwords, phone codes, puzzle checks, and payments. They should hand you the screen.
- Don’t treat separate Grok Bots as a lock between them. They share one kitchen — and its keys.
- At your stove, leave the “is this ok?” questions on until you’re bored of saying yes to the same safe thing.
- Saying yes does not un-cook a plate. Put the taste before it leaves.
- If they can’t see a source, they should say so — never invent a number, a customer, or the garlic.
Final check · 5 questions, no tricks
Visit every lesson and pass the five exam questions.
Field certificate
From Chat to Agents
This certifies that
a new head chef
can tell a phone call from a cook, can pick Grok Bot or Grok Build on purpose, and is cleared to start with look-and-draft jobs — tasting before anything leaves the pass.
Where to go right now
- grok.com — chat, when you want a mind across the table
- x.ai/bot — Grok Bot, download and meet your first teammate
- Grok Bot help — how their computer, approvals, and repeating jobs work
- Grok Build help — for when you are ready to try a folder on your computer
- The launch story — how the team uses bots at work