2026-08-27 · Comparison
Grok Bot vs Manus: What Each One Is Actually For
Roundups keep pairing Grok Bot with Manus as if both were a roster of named bots you staff and leave running overnight.
They are not that pair. Grok Bot vs Manus is standing named teammates on one persistent cloud computer versus a general agent product whose homepage, on 27 August 2026, offered slides, websites, design, and games. Confirm every Manus verb, price, and architecture claim on manus.im the day you buy. Grok Bot facts below were checked against the Grok Bot FAQ and computer and apps as of 25 August 2026, with plans rechecked 23 September 2026. Persistence and the shared computer are the Grok facts.
If the other name is a computer-use session inside ChatGPT, read Grok Bot vs ChatGPT Agent. If it is a desktop operator, read Grok Bot vs Claude Cowork.
Staff the overnight pack as a named Grok teammate, not as a brand comparison
You do not need a brand grid. You need a 06:00 Europe/London pack of overnight mail that a human can act on, and you need it after the laptop lid is shut.
On Grok Bot that job is a named bot with a charter, a screen, and a routine assigned to that bot. The computer is assigned to your user account, not to the bot. Every bot shares one persistent cloud computer. Screens are not security boundaries. Cookies, sessions, files, and command-line credentials are common. Deleting a bot does not remove those files or sessions. Routines die with the bot. The desk does not.
That is the product. It is not grok.com, and it is not Grok Build (Claude Code, SKILL.md, and CLAUDE.md live there). Read What Is a Grok Bot? before you paste a login. Staff Inbox Triage as the named teammate for the pack. Staff Mail Cleanup Assistant only if cleanup is a different job with a different stop line. Both sit on the same computer.
Reconfirm Manus on manus.im before you treat any recap as a contract
Manus is live at manus.im. On 27 August 2026 it branded itself Hands On AI, used "Less structure, more intelligence," and showed Create slides, Build website, Design, and Create games. About currently says Manus builds general AI agents as the Action Engine for life. Docs currently call it an autonomous general AI agent that takes action rather than only answering. That names the object: a general agent product. Confirm each surface live before you staff it like a Grok bot.
| Manus page currently live | What it currently describes (confirm today) | What this article will not assert |
|---|---|---|
| manus.im | Slides, websites, design, games on a general agent homepage | That those tiles are the whole product tomorrow |
| Docs and pricing | An autonomous general agent, credit-shaped plans, computer and sandbox language, and on one card the phrase Free Cloud Computer | A VM you can inventory, a frozen dollar figure, or a Grok-style account computer |
| Mail Manus | Forward, send, or CC to turn mail into tasks | That Mail Manus is a standing named Grok-style teammate |
| Browser Operator, scheduled tasks, Projects | Local-session extension, recurring natural-language tasks, persistent workspaces with a master instruction | A Grok routine, a Grok screen, or the xAI account computer |
The pricing page currently showed a restore-account banner about recent data deletion. Help pages currently discuss a service change as Manus prepares to operate independently. Confirm those notices. They are why "whatever Manus is this week" is the honest Manus column. The membership pricing help article currently names Free, Pro, and Team, then says everything is subject to the actual pricing page. Believe that last line.
Fork Grok Bot vs Manus on standing named teammates versus a general agent product
The search wants a winner. The job wants a shape. Grok Bot is a roster: name, brief, routine, still there on Tuesday with last night's file. Manus, as currently marketed, is a general agent product: you describe work, it currently claims to deliver finished artefacts, and it currently also sells websites, slides, mail-triggered tasks, a browser extension, scheduled tasks, and projects. Confirm which of those you actually opened.
| Decision | Grok Bot (documented) | Manus (confirm live) |
|---|---|---|
| What you create | A named bot, a screen, optional routines | Currently a task, a project, a workflow email, a scheduled task, or a prompt. Confirm on manus.im |
| What exists next Tuesday | The bot, its screen, the shared computer, last night's file if you wrote one | Whatever Manus currently persists for that task or project. Do not assume a named teammate |
| Who owns 06:00 | The bot you assigned the routine to | You, unless a live Manus scheduler still holds that job |
| Deleting the worker | Routines die. Files and sessions remain | Confirm what deleting a task, project, or workflow email leaves behind |
| Isolation between names | None. Screens are not a wall | Confirm. Do not invent a per-name VM, and do not invent the lack of one |
If two rows fight, persistence wins.
| Job | Pick | Why |
|---|---|---|
| Overnight inbox pack, draft only, same owner every weekday | Grok Bot | Named teammate, routine, shared computer that outlasts the lid |
| One slide deck or a website from a prompt this afternoon | Manus, if that tile is still what manus.im is selling | General agent product currently marketing delivered work. Confirm live |
| Forward one thorny thread and get a summary back in mail | Manus Mail Manus, if that page still describes that flow | Currently an email-triggered task interface. Confirm. Not a Grok roster |
| Two inboxes that must never share cookies | Neither, on one Grok Bot account | Split accounts. A second bot name is another screen |
| Standing Chief of Staff Briefing that never distributes | Grok Bot | Same desk, same refusal, last week's file |
Put every Grok bot on the one persistent cloud computer assigned to the user
Roundups get this sentence wrong, and it decides whether Grok Bot vs Manus is even a comparison.
All bots on a Grok Bot account share one persistent cloud computer assigned to the user, not to a bot. Ten named bots are ten screens and one filesystem. Connect Gmail for the pack and that session is on the computer. The research bot you add on Thursday can see it. Deleting the research bot does not log the pack desk out. Read One Computer, Many Screens.
The computer is a managed Linux VM. The bot runs as a non-root user. That is not a Linux desktop client. Clients: macOS (Apple silicon and Intel), Windows (x64 and Arm64), iPhone on iOS 18 or later. There are Linux desktop and Android apps as of September 2026, and the iOS app also runs on iPad (iPadOS 18 or later). See supported platforms. From the phone app (iPhone or Android) you can approve steps and pause or resume a routine, but not edit it. A routine assigns a workflow to one bot. Max 50 routines. Twenty recent run records. Deleting a bot deletes its routines. Nothing is team-level. No model picker. No audit view outside Enterprise.
Cloud work continues after you close the app or pocket the iPhone. Local file actions still need that machine awake. Sends set to require approval still wait on you. Sleep is not approval. Approvals do not reverse work already completed. See Grok Bot With the Laptop Closed and approvals, rules, reversibility. Beta launched 11 August 2026. Eligibility widened 21 August 2026. Still one computer per account.
Refuse to turn Manus sandbox copy into a has-or-lacks-VM claim
Manus currently uses computer language. Docs currently tell you to think of Manus as a virtual colleague with its own computer, and currently describe a sandbox with a file system. A pricing card currently includes the phrase Free Cloud Computer. The vs-ChatGPT page currently talks about a cloud sandbox with a file system, a terminal, and command execution. Confirm those sentences on Manus the day you care.
This article will not convert that copy into a VM inventory. It will not claim Manus has a virtual machine. It will not claim Manus lacks one.
Grok Bot is the column where the computer is documented as a managed Linux VM assigned to the user account, with a non-root bot process, screens that are not isolation, and deletion that does not wipe the desk. Do not paste that sentence into the Manus column to make the table tidy. If a roundup says Grok Bot vs Manus is two clouds, ask which computer is assigned to the user and what survives deletion. On Grok Bot those answers are in the FAQ. On Manus they belong on manus.im/docs today.
Run the overnight inbox pack as the only job that decides the fork
Use one job both products can pretend to cover: the overnight inbox pack.
You are a founder. Overnight mail arrives in one Gmail. At 06:00 Europe/London you want a draft pack with three buckets: customers, vendors, and noise. Must-read cap: seven threads. Each line: sender, subject, one-line stake, recommended human action. Newsletters are a count. Money, access, and legal threads are quoted and stopped. Never send, archive, label, or forward. The pack is an internal file. Connect mail as in How to Connect Gmail to Grok Bot Without Handing Over Send, then keep send off the desk.
| Clock | Manus-shaped attempt (confirm live) | Named Grok bot attempt |
|---|---|---|
| 23:10 | Prompt manus.im, or forward threads to Mail Manus if that flow still exists | Overnight Pack Desk already exists. Open last night's /packs file |
| 23:40 | A finished artefact in a task, email, or project. Confirm what still exists after you close the tab | A routine is assigned to this bot, not to the team |
| 06:00 | Nothing runs unless a live Manus scheduled task still owns that clock | The routine fires on the shared cloud computer |
| 06:12 | You are asleep. Ownership is whatever Manus currently persisted | The bot writes /packs/YYYY-MM-DD.md |
| Next Tuesday | You remember the prompt, or you do not. Confirm whether a project held the brief | Same bot, same stop line, last week's file |
The 06:00 row is the product. A general agent can turn a forwarded thread into a summary. That does not make it a hire. A named bot keeps last night's pack. A completed task does not, unless Manus currently persists that object the way a Grok bot persists. Confirm rather than hoping. This article will not treat a Manus project name as a Grok bot, and it will not treat a scheduled task as a Grok routine.
Write the pack to a file on the shared computer and never send it
A named bot without a stop line is a general agent with a longer memory and a wider blast radius. Paste a charter before you connect Gmail. This one assumes the computer is shared on purpose.
You are Overnight Pack Desk.
WHAT YOU OWN
Every weekday at 06:00 Europe/London, draft an overnight inbox pack
from mail that arrived since 18:00 yesterday. Write
/packs/YYYY-MM-DD.md and copy it to /packs/latest.md.
Buckets: customers, vendors, noise. Must-read cap: seven threads.
Each must-read line: sender, subject, one-line stake, recommended
human action. Newsletters: count only. Money, access, or legal:
quote and stop.
You sit on one persistent cloud computer assigned to the user
account, not to you. Other bots share cookies, sessions, files,
and CLI credentials. Your screen is a work surface, not a wall.
WHERE YOU STOP
Never send, reply, forward, archive, label, or delete mail.
Never submit a form. Never create, update, or delete calendar
or CRM records. Never sign into a new site. If a login expired,
write BLOCKED and stop. Do not guess.
IF YOU ARE UNSURE
Ask me. Waiting is correct. Inventing a customer emergency is not.
That charter is the whole product on a bot you intend to leave running. It is costume on a one-off Manus prompt. Inbox Triage never sends. Chief of Staff Briefing never distributes. Write the verb you are afraid of, then keep the bot off that verb.
Assign the routine to Overnight Pack Desk only. Max 50 routines. Twenty recent run records. Delete the bot and the 06:00 job dies. Signed-in sessions do not. Rotate those yourself. Scheduling traps: How to Schedule a Grok Bot Routine That Does Not Fail Silently. Prefer read-only. Least privilege. Grok Bot safety checklist.
If you try the same pack on Manus, confirm the live path: a prompt, Mail Manus, a project, a scheduled task, or a workflow email. Confirm whether send is possible on that path. Do not paste the Grok stop line into Manus and assume it binds the same way.
Buy Grok Bot on the Cursor and SuperGrok doors that actually include it
| Path | Grok Bot included? | What to remember |
|---|---|---|
| Cursor Hobby | No | Free Cursor does not include the bot runtime |
| Cursor Pro at 20 dollars a month | Yes | Cheapest paid path, checked 23 September 2026 |
| Cursor Pro+ at 60 dollars a month | Yes | More weekly usage than Pro |
| SuperGrok (individual) | Yes, by linking | Link it from the Grok Bot plan screen; it grants usage and is not a Cursor plan |
| SuperGrok Plus | Yes, by linking | Never stacks with a Cursor plan |
| SuperGrok Heavy (linked), Cursor Ultra, any seat on a self-serve Cursor Teams plan, one-time trial | Eligible | Confirm live SuperGrok Heavy pricing. Do not trust a viral 300 dollar Heavy figure |
| Manus plans | Confirm on manus.im/pricing | Do not invent a dollar figure, a credit pack, or a VM surcharge |
There is no Grok Bot-specific spend cap, but the account-level On-demand monthly limit applies. Weekly allowance, then on-demand from model and token cost. No published dollar figure for the allowance. Never invent one. No model picker. If both a Cursor and a SuperGrok subscription are present, Grok Bot uses whichever has more usage. See Grok Bot Cost and spend cap and token burn.
Model Grok Bot as 20 dollars on Cursor Pro (or 60 on Pro+, 200 on Ultra, or a Teams seat) plus overflow up to the On-demand monthly limit you set. A lower Manus entry price, if one still exists on your region of the pricing page, is a good reason to run a one-off pack in a general agent. It is a bad reason to staff a standing 06:00 owner on a task that might not be there on Tuesday.
Manus currently describes credits on Plans and Pricing and shows live numbers on pricing. Docs currently name Free, Pro, and Team. One card currently prints Free Cloud Computer. This article will not print a Manus dollar price as fact. Help copy currently says everything is subject to the actual pricing page. Confirm the meter, scheduled-task cap, and mail address on your account. Do not map Manus credits onto Grok Bot's unpublished weekly allowance.
Treat a second Grok bot name as another screen, never as another security domain
The expensive Grok Bot mistake in this comparison is staffing Overnight Pack Desk and a scout, then believing you bought two computers because Manus currently talks about sandboxes.
You bought two screens. The Gmail session is account-wide. Naming does not partition credentials. Deleting the scout after a scare does not log Pack Desk out. Prefer read-only. Put money and sending on a different account from draft packs. Write the stop line before you paste a login. When a bot is done, rotate the sessions yourself.
On Manus, blast radius is whatever the live product can touch on the path you chose. Browser Operator currently describes using your authentic local IP and existing logins. Confirm that. Do not treat it as the xAI shared computer, and do not treat it as proof Manus lacks a cloud environment. You have not been given a VM inventory either way. Hosted MCP sign-in tokens on the Grok Bot side stay with Cursor's backend, not on the computer. There is still no audit view of Grok Bot actions outside Enterprise. Confirm whether Manus currently sells an audit trail. Do not invent it.
Trace the failure where a Manus task and a Grok routine were treated as the same object
When the week goes wrong, name the object before you rewrite the prompt.
| Symptom | Likely cause | Fix |
|---|---|---|
| Nothing ran at 06:00 in Manus | You treated a completed task as a standing named worker | Put the pack on a Grok Bot routine, or confirm a live Manus scheduled task still owns that clock |
| Two Grok bots used the same Gmail cookies | Shared computer, by design | Treat the account as one security domain |
| You deleted Overnight Pack Desk and Gmail is still signed in | Deletion does not wipe files or sessions | Rotate the session yourself |
| A Manus mail workflow sent or logged something you only wanted drafted | A general agent path that currently includes action verbs | Confirm Mail Manus prompts live. Put send off the Grok charter |
| Grok Bot never appeared on your Linux laptop | An installer story from before September 2026 | There is a Linux desktop app as of September 2026 (.deb, .rpm, AppImage) |
| Thursday's pack cannot see Wednesday's file | You used a one-off task, not a desk | Named bot plus a folder on the shared computer |
| iPhone could not edit the 06:00 routine | phone app can pause and approve but not edit | Change the routine on desktop |
If the job is a supplier portal every Monday, that is a different comparison. Recover files from the shared computer if they remain after a bot is deleted. Routines will not remain.
Concede the case where a general agent task is enough for one pack
The strongest case against this article is simple: if Manus can already turn mail into a summary, naming a Grok bot is costume. For a large class of jobs, that case wins.
It wins on the one-off thread you will never staff, on decks and websites if those tiles are still what manus.im sells, and on friction. Opening manus.im is closer to a chat than naming a bot and assigning a routine. If you will only ever want one pack, do not build a roster. Creating Overnight Pack Desk for Thursday, then deleting it Friday, leaves the Gmail session on the shared computer.
It loses when the name has to survive. Customers, vendors, noise, seven must-reads, 06:00, last night's file, a refusal to send: those jobs stay valuable because they keep existing with the same stop list. A general agent can imitate that if you are the memory every night, or if a live Manus project plus a live scheduled task currently hold the brief. Confirm that combination. Most people skip a night, the prompt drifts, and a send verb creeps back in. A Grok Bot routine can fire while you sleep. Confirm any Manus continuation on Manus. Do not import the Grok lid sentence into the Manus column.
Verify the choice with checks that fail if Tuesday still has no named owner
Open manus.im today. If the first tiles are still slides, websites, design, and games, you are looking at a general agent product, not a Grok roster. Open manus.im/pricing. If you cannot see live credit copy, you are not ready to budget Manus. If you see Free Cloud Computer on a card, write it down as a phrase, not as a VM you measured.
Name the Grok object: one persistent cloud computer per account, screens not walls, routines per bot, no per-Bot spend cap, no model picker, a Linux desktop app since September 2026. Create Overnight Pack Desk, assign one weekday routine, close the laptop. In the morning the pack file is either there or it is not. On Manus, run one pack as a task and ask the next morning whether a named worker still owns 06:00 without you.
Connect Gmail on Grok Bot only after the charter forbids send. Then add a second bot and notice that it can see the same session. If that surprise makes the pack unsafe, you wanted two accounts, not two names.
Keep Manus for delivered work and Grok Bot for a named pack that still exists
Keep both only if you can name which object owns which job.
Keep Manus, if manus.im still describes it this way, for delivered artefacts: a deck, a site, a one-off research pack, a forwarded thread you will never run again. Confirm Mail Manus, scheduled tasks, projects, and Browser Operator on their current pages. Hedge every price and every computer word. Do not staff Manus as a Grok-style roster unless Manus currently sells that object in words you can quote.
Keep Grok Bot for unfinished work that wants a name, a charter, a screen, a routine, and last night's inbox pack. Staff few bots. Connect few accounts. Write the verb that must never happen. Every bot shares the computer. Deletion is not cleanup. Overflow has no per-bot cap, only the account's On-demand monthly limit. There is a Linux desktop app as of September 2026 (.deb, .rpm or AppImage). The phone app (iPhone or Android) can pause the routine and approve steps but cannot edit it.
A general agent returns work you asked for tonight. A named bot is still there on Monday, on a shared computer whose blast radius you accepted on purpose.
Keep reading: Grok Bot vs ChatGPT Agent: Computer Use Against Named Bots, Grok Bot vs Claude Cowork: Cloud Teammate or Desktop Operator, What Is a Grok Bot? The Plain Explanation for Non-Engineers.
Frequently Asked Questions
Is Manus a named-bot product the way Grok Bot is?
No. Grok Bot is a roster of named bots on one persistent cloud computer assigned to your user account, with a screen per bot and routines assigned to one bot. Manus currently markets itself as a general AI agent product. Confirm the live object on manus.im, including tasks, projects, Mail Manus, and scheduled tasks. Those currently look like a general agent with extra surfaces, not like Grok Bot screens. Do not treat a project name as a Grok teammate until Manus's current docs say that in words you can quote.
Does Manus give you a virtual machine?
This article will not assert that Manus has a virtual machine, and it will not assert that Manus lacks one. Manus currently uses computer and sandbox language on its docs and currently prints Free Cloud Computer on a pricing card. Confirm those sentences on manus.im. Grok Bot does have one persistent cloud computer per account, a managed Linux VM where bots run as a non-root user, with a screen per bot. That computer is not a Linux desktop app, and it is not a private VM per bot.
Can a Grok Bot write an overnight inbox pack with the laptop closed?
Cloud work can. Grok Bot runs on a persistent cloud computer assigned to your user account. A routine assigned to one bot can fire while the laptop is shut, the app is closed, or the iPhone is in your pocket. Local-computer actions still need that machine awake. Sends, publishes, and purchases set to require approval still wait on you. Sleep is not an approval. Confirm the lid behaviour in the closed-laptop guide rather than treating every overnight pack as unattended.
Is Manus cheaper than Grok Bot?
Grok Bot's cheapest paid path is Cursor Pro at 20 dollars a month. Every paid Cursor plan includes Grok Bot, from Cursor Pro at $20; Cursor Hobby, the free plan, does not, and an individual SuperGrok, SuperGrok Plus, SuperGrok Heavy or X Premium+ subscription can be linked instead. Cursor Teams include it. There is no Grok Bot-specific spend cap, but the account-level On-demand monthly limit applies: weekly allowance first, then on-demand up to that limit, with no published dollar figure for the allowance. Manus prices and credits belong on manus.im/pricing. This article will not invent them. Confirm both the day you buy, including whether the live Manus plan still matches last month's help article.