Build Your First AI Teammate.
Adapted from "The ONLY Grok Bot Tutorial You Need 2026: How To Use Grok Bot For Beginners"
Then the team.
A Team Of Bots With Their Own Screens.
The video tours Grok Bot for beginners. Each bot works as a teammate with its own cloud computer, browser, and screen you watch. The creator builds an executive assistant first, connects accounts, teaches tasks on the bot's screen, schedules routines, adds specialists, and coordinates them in group threads. One caveat runs under every demo: every bot shares one computer and one set of logins.
Paid plans only.
Download the desktop app from x.ai/bot. Grok Bot has no free tier. The creator pays $100 a month for Grok Plus. Cheaper plans differ by usage, and light users fit the beginner tier. An eligible Cursor, SuperGrok, or Teams plan includes Grok Bot at no extra cost.
The executive assistant comes first.
Plus button, create new bot, name the bot, add a short description, and leave notifications on for moments the bot needs input. The new bot asks what to own. His answer: day-to-day ops and miscellaneous tasks. He says the bot learns preferences over time and builds routines when asked.
Settings before tasks.
The usage and billing meter stops all work at 100 percent until the period resets or you buy more. Update the app and the bot's Linux computer every so often. Reset the computer when stuck, and rarely.
Two ways to connect accounts.
Ask in chat ("connect my email accounts"), then log in, for example a second Gmail named work. Or connect one MCP hub such as Composio or Zapier once, and add every tool inside the hub. He calls the hub the better route for anyone with many logins.
Every teammate has a screen.
Click the screen icon and the bot's desktop opens. You open Chrome, log in, and work on the same machine. His assistant has placed Amazon orders, downloaded and filled out documents, and chatted with customer service agents on his behalf.
Teach by doing.
A button at the top right starts a session where you perform a task on the bot's computer while the bot watches and learns. Ask "do this on your computer so I can see it" to watch a live run. Demo: three best soundbars under $500 on Amazon, returned with links. Buying needs your login and permission. He notes the bot moves slower than a person.
One owner per bot.
Every bot besides the executive assistant and a chief of staff owns one specific thing. The chief of staff coordinates the other bots for business owners. Researchers come next, and he runs several.
Bots message each other.
The assistant asks a researcher for something, the researcher answers back, and none of the exchange needs your input. He sees his agents talk to each other all the time and describes the result as a team working together.
Routines run the schedule.
Each bot lists its routines in a right panel. His assistant runs three, including a weekday morning brief. Example: "Every morning at 9:00 a.m., look through my Slack and email and send me a report." Tell the assistant about your life and routines, then ask which routines to set up.
His roster.
A finance bot chases invoices, emails clients, reads QuickBooks, and sends reports. A newsletter bot logs into Beehiiv and finds news. An assistant runs his overseas recruiting company. Plus a content strategist, several researchers, and a LinkedIn outreach bot. Roster size follows business complexity.
Marketplace, plugins, group threads.
Import prebuilt bots, including one built to interview you and design bots. Featured plugins cover Gmail, Drive, Calendar, Slack, and Notion. A password manager connection logs bots in, with his claim the password never reaches the bot. Group threads put several bots in one chat for visibility: assistant, finance, and COO coordinate on outstanding invoices in view.
Email from chat, one shared computer.
"Any emails I should respond to? Brief me." returned four items, and "Reply to Lisa saying thanks" sent the reply on the thread. The caveat: every bot shares one cloud computer, with the same files, browser, and logins. One bot in your email means every bot reaches your email. You tell bots to stay out of accounts, and the setup allows nothing stronger today. The video closes on a free community and affiliate links. The transcript spells the product "Grokbot" and "Grockit."
Build Your First AI Teammate.
Core MessageYou built six bots in one afternoon, and a week later none of them run anything. Hire one assistant first. Write what the assistant owns. Connect only the accounts a named task needs. Show the task on the assistant's screen and watch three runs. Promote the third repeat to a routine. Add a second teammate only when a job keeps coming back, and keep every handoff in a thread you read. One teammate running your mornings beats six waiting for a message.
TargetEarly career, solo or junior, no assistant, no ops budget, and an agent app full of idle bots.
Opening QuestionWhat would your first assistant own on Monday, in one sentence?
Six Bots. Zero Routines.
You watched a tour of an agent app, and the roster looked like a company: assistant, chief of staff, finance, researcher, outreach. So you built six bots in one sitting. Each one asked what to own, and you typed "help me with whatever comes up."
A week later you open the app and every bot waits for a message. Nothing ran on schedule. Nothing improved. The bots learned nothing about your work, because you never showed them any work. Two are still logged into your email, and you no longer remember why.
The standard advice says add more agents and let them coordinate. A bigger roster multiplies the problem. More bots with no job means more places to check and more logins on one shared machine. The creator's own setup started with one executive assistant, and the order he teaches holds: a job, the accounts the job needs, a demonstration, a schedule, then teammates.
A new hire starts with one desk, a written job, a week of shadowing, and a standing schedule. Your first agent needs the same onboarding.
Five Steps To One Working Teammate.
One Seat.
One Card.
The demo bot asked what to own, and the answer was day-to-day ops and miscellaneous tasks. Miscellaneous is no job. A bot without a defined job waits for prompts, and a bot waiting for prompts is a chat window with a name. Start with one executive assistant and write the ownership card before the first message.
- 01List the week
Write every recurring admin task from last week: inbox triage, scheduling, follow-ups, invoices, research, forms.
- 02Pick three
Circle the three tasks you repeat at least weekly and resent most. Everything else stays yours for now.
- 03Write the card
OWNS (the three tasks in one sentence). RETURNS (format and time). ASK FIRST (money, client messages, anything public). NEVER (purchases, deletions, passwords in chat). REPORTS TO (you, by name).
- 04Paste the card
Send the card as the first message. Ask the assistant to restate the job in two lines and to ask up to three questions.
- 05Hold the roster
No second bot this week. A second seat too early doubles the noise.
If the job needs two sentences, the assistant owns nothing.
Connect The Keys
The Job Needs.
Every Grok Bot teammate shares one cloud computer: the same files, the same browser, the same logins. Log one bot into your email and every bot reaches your email. The video's answer is an instruction telling certain bots to stay out. An instruction is a request, not a lock. Treat every login as a login for the whole team.
- 01Match account to task
Connect an account only when a task on the card needs the account. No task, no login.
- 02Climb the ladder
Read first. Draft second. Act third. Move one rung per account after two clean weeks on the rung below.
- 03Use one hub
Past three tools, connect through one hub such as Composio or Zapier, and scope each app to the actions the card names.
- 04Keep secrets out of chat
Use a password manager connection or log in yourself on the bot's screen. Never paste passwords, card numbers, or ID numbers into a message.
- 05Watch the meter
Check usage on the first of each month. At 100 percent, every bot stops until the reset.
Every login is a login for every bot.
Show The Job
On The Screen.
Each bot has its own desktop, browser, and a teach button. Press the button, do the task on the bot's computer, and the bot watches. Then ask the bot to work on its screen so you see every click. The soundbar demo stopped at three links. Nobody watched a purchase, a form, or a send. Shadowing runs both ways: the bot watches you once, then you watch the bot three times.
- 01Teach once
Perform the task on the bot's computer start to finish. Say each decision out loud in one sentence while you work.
- 02Run on screen
Assign the same task with "do this on your computer so I see each step."
- 03Watch three runs
Log every wrong click, wrong field, and wrong assumption in a fix log, one line each.
- 04One rule per fix
Send each fix to the assistant as a one-line rule for the job. Repeat fixes mean the rule is unclear.
- 05Keep the final click
Purchases, submissions, and sends stop one screen before the button. You press the button with money or your name behind the button.
Watch three runs before you trust one.
Promote The
Third Repeat.
A routine runs on a schedule with no message from you: "Every morning at 9:00 a.m., look through my Slack and email and send me a report." The video adds a shortcut: describe your week and ask the assistant which routines to set up. Suggestions arrive in bulk, and routines pile up the same way bots do. Promote by evidence instead. A request you sent three times in one month earns a schedule.
- 01Count repeats
Scroll back through the month's chat. Mark every request you sent three or more times.
- 02Write the routine card
WHEN (days and time, ET). READS (sources). RETURNS (format and length). QUIET (what counts as nothing to report). NEVER.
- 03Write the quiet line
Most mornings hold nothing urgent. On those days the report reads "Nothing needs you today" in one line.
- 04Add one per week
One new routine per week. Three routines max in month one.
- 05Read on Friday
Mark each run useful, noise, or wrong. Two noise weeks in a row, cut the routine.
The third repeat earns a routine. The first one earns a chat.
Add Teammates
In The Open.
Bots in the video message each other on their own. The assistant asks the researcher, the researcher answers, and you never see the exchange unless you open a group thread. The creator built group threads for visibility. For a new professional, visibility is the default. Add a specialist only when a job proves the need, and route every handoff through a thread you read.
- 01Earn the second seat
Add a specialist when one job type shows up three or more times a week and needs context the assistant should not carry, such as client books or research notes.
- 02Write the card first
Same five lines. One job. One return format. Same NEVER list as the assistant, plus anything the job adds.
- 03Open a team thread
Put the assistant and the specialist in one group thread. Route all money and client work there.
- 04Read handoffs daily
Five minutes a day. Check what each bot asked, what came back, and what moved.
- 05Hold the cap
Three bots max in month one: the assistant plus two specialists earned by evidence.
No private side channel on money or clients.
One Consultant. One Seat.
Here is the five-part setup applied to one new professional over one month.
Planning figures. Log four weeks and replace every number with your own.
Six Prompts. One Hire.
You are my executive assistant. Here is your card. OWNS: [three tasks]. RETURNS: [format] by [time] ET. ASK FIRST: any message to a client, anything involving money, anything public. NEVER: purchase, delete, or send without my yes. Never ask me for a password in chat. Restate your job in two lines, then ask me up to three questions before your first task.
Do this task on your computer so I see each step: [task]. Stop one screen before any submit, send, or buy button and wait for me. When you finish, list each decision you made in one line.
Add this rule to your job: [one-line fix]. Confirm the rule in one line and tell me which past step the rule would have changed.
Create a routine. WHEN: [days] at [time] ET. READS: [sources]. RETURNS: [format and length]. If nothing needs me, send one line: Nothing needs you today. NEVER: send, reply, buy, or schedule on my behalf.
You are my [role]. OWNS: [one job]. RETURNS: [format]. Work with my assistant only in the team thread named [name]. Never message a client or move money.
List every task you ran this week, every routine run, every account you touched, and every message you exchanged with another bot. Mark anything you guessed at.
Card fields: OWNS, RETURNS, ASK FIRST, NEVER, REPORTS TO. Routine fields: WHEN, READS, RETURNS, QUIET, NEVER.
Read This Before You Build Six.
A tour, not a test.
The video shows setup. No bot appears running for a week, and no result gets measured.
One computer holds every key.
Shared files, browser, and logins. An instruction to stay out of an account is not a permission setting.
The demos stop short.
The soundbar search ended at links. The invoice thread cut away before an answer came back.
Sends from chat skip review.
"Reply to Lisa saying thanks" went out from one line, with no draft shown first.
Private bot chats hide decisions.
Bots talk to each other by default. Visibility takes a group thread you open on purpose.
Usage runs out.
At 100 percent every bot stops. The $100 plan is the creator's, with no usage numbers on screen.
Your name rides along.
Orders and customer service chats on your behalf carry your account, your address, and your liability.
Tutor, mentor, therapist overstates the job.
A bot reading your inbox is an assistant, not a counselor or a coach.
The pitch comes with the tour.
The video closes on a free community and affiliate links in the description.
Names age fast.
The transcript spells the product two ways. Card, keys, screen, routine, and room carry over to any agent platform.
Seven Days. One Hire.
Delete the bots with no card. Keep one seat. Run the week below before you add anyone else.
- D1List last week's admin tasks. Pick the three you repeat and resent most.
- D2Write the five-line card. Create one assistant and paste the card first.
- D3Connect one account, read only. Start the access list.
- D4Teach one task on the bot's screen. Watch the first run and log fixes.
- D5Watch runs two and three. Turn each fix into a one-line rule.
- D6Schedule one routine with a quiet line. Confirm the first run lands.
- D7Friday review. Mark each run, cut one thing, decide whether a second seat is earned.
Hire one. Show the job. Schedule the repeat. Then hire two.
Join the AigentLab
Build your systems with other solo builders.