What Is Grok Bot, and How Should a Business Use It?

Grok Bot is xAI’s app for named AI teammates that keep a cloud computer, remember how your company likes a job done, and finish multi-step work across tools you already use. Use it for repeatable internal jobs that have a named source and a hard stop before anything is sent, paid, posted, deleted, or written into a customer record. It is not the Grok chat assistant. It is also not your website, your ads account, or a very confident intern you can leave alone with the company card.

This guide is written by Stephen Prager, founder of Prager Microsystems in Collegeville, Pennsylvania. We have built and measured how companies actually operate since 2003, which is long enough to recognize a shiny tool with a login and no job. The product facts below were checked on October 20, 2026 against xAI’s own Grok Bot documentation. Plan names will move. The standard should not. We call it SCOPE.

What is Grok Bot?

xAI introduced Grok Bot on August 11, 2026, and called it a team of agents that stay on. The useful distinction is less glamorous than the launch language, which is usually a good sign. A chatbot hands you an answer. A Bot gets an outcome, some access, and a fence, then it is supposed to come back with finished work or a sensible question. A confident short story is not one of the options.

That is why the first decision is the name, and why “Assistant” is a terrible one. Assistant of what, exactly? “Renewals,” “Briefing,” and “Meeting prep” are jobs. Tell a Bot to help with the business and it will wander, because “the business” is not a task. It is a mood. Give it one repeatable outcome and you can correct it, save it, and eventually trust it with a calendar.

You talk to a Bot the way you would text a coworker, from the desktop app or the phone. Same Bots, same conversations, same routines, same shared computer. Type it, dictate it, attach a file, or start a voice conversation. None of that helps if the message is “you know, the usual.” Name the outcome.

Bot

A named role with a memory, a job description, and access only to what that job needs. “Assistant” does not qualify. “Renewals” does.

Skill

The method, written down after it has worked. It names the inputs, the steps, the checks, the output, and the line where a human still has to say yes. A skill can be shared. The Bot still needs the login the skill assumes. Optimism is not a connector.

Routine

The instruction for when one Bot runs that method, on a schedule or after an event the product supports. A routine without a proven skill just puts a mistake on a clock and calls it operations.

Shared computer

The cloud machine for the whole account. Every Bot on it can see the files, the signed-in browser, and credentials used at the command line. Yes, including the one you named Intern.

How is Grok Bot different from Grok?

People burn a week interviewing the Bot about its capabilities. They ask what it can do, collect a list, and never hand it a file. That is like hiring someone and spending the first week asking them to describe a spreadsheet. Do it the other way. Describe one job. It asks for access as the job needs it. You correct the result. Then you save the path so you do not have to explain it again.

There is a second way to mix this up, and it is public. On X, @grok is the assistant people tag when they want a reply under a post. @bot is a different handle. Tag @bot and that post can become a task for the main Bot on a connected account. Its public reply is basically a receipt, not a conversation. Do not tag @bot under a post you would hate to see treated as an instruction. Especially not a joke. Bots are not famous for getting those.

What does a Bot actually have?

xAI’s overview, current as of our October 20, 2026 check, describes five traits that matter once this thing is inside a real company and not a demo.

• A computer that stays on. Browser, files, and a terminal. A connector where a connector exists. The computer itself for everything else, including the dusty site with no API. Closing your laptop does not close the job. It just means you are no longer watching.
• Setup by message. You do not start with a flowchart and a workshop. You create a Bot, describe the job, and grant access when it asks. The same Bot is on the desktop app and the phone.
• Other Bots. They can work at the same time, message each other, share a group chat, and hand off a task. You do not have to be the switchboard. You do have to be the person who drew the fence.
• Learning from a demonstration. Walk the path once, like you would with a new hire. Save it as a skill. Put it on a schedule only after the path is dull and correct. Dull is the goal. Dull means it stopped improvising.
• Context that compounds. A named Bot keeps memory, files, browser sessions, and preferences. That is the point, and it is also how a small mistake becomes house style. A correction you do not say out loud will not stick. A login you leave open stays open for every Bot on the account.

A good first message is not a manifesto. It has four parts, in plain language: the outcome, the sources, the constraints, and what finished looks like. Read what comes back. Correct it in the same thread, where the Bot can actually hear you. When the path stops surprising you, save it as a skill. Only then does it get a clock.

What is the Prager SCOPE standard?

SCOPE is an assignment test, not a poster for the break room. If you cannot write a letter in one or two sentences, you do not have that letter yet.

1. SSourceThe file, inbox, calendar, or public page the fact comes from. “Look around” is a vibe, not a source.
2. CConstraintThe verbs it does not get. Email, pay, post, delete, and change a customer record are the usual suspects.
3. OOutcomeWhat done looks like, on one screen. A list, a one-page brief, or a folder of drafts. Not “make it better.”
4. PPermissionThe actions that wait for a human. If two rules argue, “ask first” wins.
5. EEvidenceA file name, a URL, or the word UNVERIFIED. A naked number is just a number with confidence.

We wrote SCOPE because the failure is boringly predictable. A company gives a Bot a fun personality and a pile of logins, then acts shocked when Thursday’s brief invents a renewal date that was never in the file. The Bot did not have a moment. Vague instructions have a hole, and a confident model will spackle it. SCOPE makes you look at the hole before you hand over the password.

Evidence is the letter everybody skips, usually while nodding. A brief that says a contract renews on June 1 is useful only if it also says which file said June 1. If the file does not say it, the line is UNVERIFIED. That slightly awkward word is what stops a smooth paragraph from becoming a decision nobody can unwind.

How do you create the first Grok Bot for a business?

1. Confirm the account actually includes Grok Bot. Access has been tied to specific paid plans since the August 11, 2026 launch, and that menu has already moved. Read the current plan page before anyone puts a number in a budget. Bot usage is not the same pool as chat messages. Finding that out mid-demo is a special kind of meeting.
2. Install the app, sign in, and create one Bot. Name it for the outcome, not the company. “Renewals” beats “Office assistant,” and it beats your own name, which we have seen, and which helps nobody.
3. Write the description as a fence. Say what the Bot owns, what it must never do, and that missing evidence gets marked UNVERIFIED instead of invented.
4. Hand it one task that needs no new logins if you can. Attach the file. Ask for one screen of output, plus a separate list of anything it could not confirm. The second list is the interesting one.
5. Read the result against the source. Correct the misses in the same thread. Do not schedule it. You are not there yet. You are at “this did not embarrass us.”
6. Connect a tool only when the corrected task cannot be finished without it. Take the narrowest access the other system allows. Start with permission to read. Changing things can wait until the Bot has earned the privilege, which is a high bar.
7. Save the corrected path as a skill. Give it a routine only after a second run matches the first. Two good runs. Not one good run and a feeling.

The phone is the right place to approve a step or read a result from a parking lot. As of the mobile docs we checked on October 20, 2026, editing a routine’s schedule still belongs on the desktop app. Find that out on purpose. Do not find it out on a Monday morning, while the brief is wrong and the coffee is still too hot to be useful.

How do you turn a task into a skill?

Ask in the same thread, after the result is actually right. Not after it is charming. Right.

Save the process we just used as a skill called “Monday renewal list.”
Include the source file, the window of 45 days, the output columns, and the rule that a date not present in the file is UNVERIFIED.
Include the rule that emailing, paying, or editing the file always requires my approval.
Do not run it on a schedule yet.

If you cannot read a skill aloud in under a minute, it is hiding a second job. Split it. Renewals does not also book flights. Briefing does not also call the vendor to “just see what’s up.” One outcome is how you notice the skill has started freelancing.

How do you schedule a routine without automating a mistake?

Every Monday at 8:00 AM Eastern, run the Monday renewal list skill against the current file.
Post the list in this conversation.
If the file is missing or unreadable, say so in one line and stop.
Do not use last week’s list.
Do not email, pay, or edit anything.

Skip that shape and the first month produces three classics. The routine runs on last month’s export and sounds extremely current. The routine emails a vendor because somebody left the words “follow up” in the skill, and the Bot heard a verb. The routine keeps firing after the source system changes, and everyone assumes someone else paused it. Pause it when the file, the folder, or the definition of done changes. A routine does not get embarrassed. You do.

On the phone you can look at the schedule, the next run, and the history, and you can pause or delete a routine, which is the button you will eventually be grateful exists. Write the instruction on the desktop, where the whole sentence fits and you can see the part that says “do not email anyone.”

Which business jobs pass SCOPE?

Notice what is missing from that table. None of those jobs is the company’s public face. A Bot can build the renewal list you read with coffee. It should not become the voice that speaks, bids, or gets the company found. Coffee is about the right level of responsibility.

A complete assignment, using renewals

This is the shape we actually keep. Change the window and the file name. Leave the stop lines alone. They are not decoration. They are the part that keeps Tuesday boring, which is the point.

You are Renewals. You own the date list. You do not own vendor relationships.

Each time I ask, or each Monday at 8:00 AM Eastern once this is a routine, read only the renewal file I attached.
List anything due in the next 45 days.
Use columns for the vendor, the date, the document name, and whether the file states that date.
If the file is missing, say so and stop.
If a date is not in the file, mark the row UNVERIFIED. Do not guess.
Do not email, call, pay, or change the file.
Post the list in this conversation and nothing else.

Which jobs stay with a person?

• Sending as the company. Email, text, social posts, and invitations wait. A draft in the thread is the finish line. The send button is a different meeting.
• Money. Paying an invoice, buying a fare, accepting a quote, or moving funds waits. The shortlist is the job. The card number is not a fun surprise for later.
• The public website and the ads account. Pages, markup, hosting, DNS, bids, and conversion tags are not Bot chores. They are the record customers and answer engines use to decide who you are. A cloud computer with a saved login is a terrible lab for that record. If the site needs to be quotable and still worth calling, that is a build, not a prompt you try on a Thursday. We wrote the build standard separately, in how to design a website answer engines can cite. The phone number for that conversation is 1-610-723-7922.
• Pricing, hiring, and legal terms. A Bot can lay out options you already trust. It cannot bind the company, pick a hire, or accept terms it did not write. “It seemed reasonable” is not a legal strategy.
• Deleting or overwriting the source. The file that proves the date is worth more than the summary of the date. A Bot that “cleans up” the source has not been tidy. It has eaten the evidence.

We are picky about the website and the ads account on purpose. Point an agent at your site, your ad accounts, or your analytics and hope for a shortcut, and you will spend the month undoing the shortcut, usually while explaining it to someone who did not ask for the adventure. Those systems are how customers find you and how the phone rings. They are a bad place for an unattended routine to get creative.

What does the shared computer change?

This is the fact people skip, even though xAI’s own security notes say it in plain language. Do not use separate Bots as a security boundary. Naming one “Finance” and another “Intern” feels like two offices. On this product it is one office, two nameplates, and a shared browser history. The login you left open so Renewals could see a spreadsheet is a login Briefing can also reach. Briefing did not need the spreadsheet. Briefing has it anyway.

Treat that computer the way you would treat the shared machine in the back office. The one everyone swears they logged out of.

• Connect only the tools this workflow needs. When the job is over, remove the connector, and revoke it at the source if you can. “We might need it later” is how later becomes a mess.
• Prefer a scoped login over the owner’s personal login whenever the other system allows one. Your personal inbox is not a company feature.
• Sign out of a site when that session should end. Deleting the Bot does not unwind a browser you forgot. The browser does not take hints.
• Delete temporary files that hold customer data, tax documents, or credentials once you have accepted the task. The cloud computer is not a junk drawer you get to forget about.
• Do not paste a password, a passkey, or a one-time code into the chat. When a site asks, take over the computer, do that step yourself, hand control back, and tell the Bot to continue. You can trust a process. You do not paste secrets into a transcript.
• Keep the Bot off your local machine unless a specific job needs local files. The default worth keeping is to ask every time, and to refuse local execution when the work already lives on the cloud computer.

Group chats and handoffs are genuinely useful once two jobs are stable. Briefing can ask Renewals for this week’s dates, and you can read that handoff. That is not a reason to give every Bot every login “so they can collaborate.” That sentence is how a wider blast radius gets described as teamwork.

What approval line should a company set?

The product can stop and ask before an action runs, and it lets you write rules. “Allow the browser” is not a rule. It is a shrug with a keyboard. “Ask first before sending any external email” is a rule. So is “you may read the renewal file in this folder, and that is the end of your adventures.”

Put that line in three places, because a person will forget at least one of them and then act surprised. Use the Bot’s description, the skill, and the routine. An approval stops a proposed action. It does not time-travel, and it will not unsend the email. That is why the first runs are allowed to read, and nothing else. Reading is reversible. Sending is a story.

Personal review rules can live on a desktop and sync to that desktop’s Bot computer. A second computer does not inherit your good judgment automatically. If two people install the app, check the rules on both before you assume Thursday morning is safe. Thursday morning is a bad time to discover a policy disagreement.

How do you write the assignment?

Fill the fields and build the assignment. The stop lines stay even if you change the job.

How do you tell whether the Bot is earning its place?

Keep a score of four lines for the first four weeks. Paper is fine. A notes app is fine. The point is that a person looks, instead of declaring victory because the Bot used complete sentences.

• Source match. Pick three claims from the latest run and find them in the file or on the page. A miss means the evidence rule is not in the skill, or you handed it “the internet” and called it a source.
• Stop line. Confirm it did not send, pay, post, delete, or edit the source. One breach and the routine pauses the same day. Not after a discussion. The same day.
• Correction count. Count the edits you made before you would trust the result. When that number is near zero for two weeks, the skill may earn a schedule. A good feeling on a Friday does not count as two weeks.
• Time returned. Compare the minutes you spent reviewing with the minutes the old process took. A Bot that creates a brand-new review meeting has not helped. It has hired you as its editor.

Retire a Bot that breaks the stop line twice, or that you cannot explain to a new hire in a minute. Extra Bots feel like momentum. Mostly they are logins nobody owns, wearing name tags. One slightly dull Bot that produces a list you actually use is the whole prize. Dull is a compliment. Dull means it stopped inventing dates.

Spend with the same mood. Grok Bot has lived in a paid tier since launch, with its own usage, separate from ordinary Grok chat. The names of those tiers have changed often enough that a dollar figure in this article would be an act of optimism. Read the current plan page. Then buy access for one job, not for a department you have not designed and a Bot named Strategy.

What else are people asking?

Product behavior, plan names, and which buttons exist on the phone will keep moving. SCOPE will not. Source, constraint, outcome, permission, evidence. If you can write those five sentences, you can hand a Bot a job. If you cannot, the job is still yours. Sorry. That is the deal.