Switch from Grok Bot to Task Machine
Grok Bot gives named Bots jobs across connected apps and a shared cloud computer. Task Machine gives people and agents owned Tasks with plans, acceptance checks and an Inbox for decisions.
Prefer the side-by-side comparison?Why people switch
-
Model choice stays hidden
Grok Bot chooses the model for each task without a model picker. Its usage views do not show the underlying provider or model name.
-
Background approvals expire
Approval cards raised by routines, incoming messages or other background work expire after 30 minutes. To finish after a card closes, you must ask the Bot to try again.
-
Some routines need rerunning
Grok Bot documents a shared rate-limit issue that can fail routines even below your own limits. A run that fails with this error is not retried automatically.
What maps to what
Every answer links to its source and shows when we last checked it. The oldest check on this page was November 15, 2026.
| Area | In Grok Bot | In Task Machine |
|---|---|---|
| Jobs |
In Grok Bot
Each Bot has a name, a job, its own conversation and working context. Your primary Bot coordinates work with the others. |
In Task Machine
Every job is a Task that a person or an agent owns. Its plan, discussion, decisions, runs and history stay together, so people and agents hand work over on the same record. |
| Workflows |
In Grok Bot
Skills capture steps, decision rules, expected output and safety boundaries. Private skills form one library shared across your Bots. |
In Task Machine
A Workflow repeats explicit steps with branches, human questions and approvals. Verifier checks judge results against requirements and send failed work back with feedback. |
| Recurring work |
In Grok Bot
A routine assigns a workflow to one Bot and starts it on a schedule or from an event, such as a Slack message, email or webhook call. |
In Task Machine
Start a Task or Workflow once or on a repeat in your timezone. A recurring job keeps one root Task and gives each occurrence its own status and history. |
| Approval |
In Grok Bot
Auto Review checks proposed actions. Custom Rules can require Ask first, and matching actions pause with an approval card in chat. |
In Task Machine
Decisions arrive in your Inbox with context. Set each agent's actions to Ask first or Automatic, and add a Human approval step before sending a report or making another consequential change. |
| Memory |
In Grok Bot
Bots retain preferences, facts and summaries across chats. Ask in chat to inspect, correct or remove a personal Bot's memory. |
In Task Machine
Agents carry lessons from corrections into later work, such as an accepted example or a mistake to avoid. You can inspect, correct and restore notes for an agent, Project, Goal, Team or workspace. |
| Execution |
In Grok Bot
Your Bots share one persistent cloud computer, including files, browser sessions and logins. Desktop commands need a separate permission. Team Bots always run in the cloud. |
In Task Machine
Run agents in Managed Cloud with nothing to install, or connect a Local Worker, a computer you control, for local files, tools and accounts. You choose where each agent runs. |
| Pricing |
In Grok Bot
Premium is $30, Super $100 and Ultra $200 a month, billed monthly. New customers use The X Subscription, where Bot usage shares a weekly pool with Cursor and Grok. Legacy accounts differ. |
In Task Machine
Usage based, from $29 a month before tax. The whole payment becomes usage that your workspace shares, with no base fee. |
A fact we cannot find or cannot check is left out, and prices can change after the date shown. Task Machine publishes this comparison and is an interested party. Grok Bot is named only to identify it, and there is no relationship between the two companies. Has something changed? Tell us.
You may stay with Grok Bot if
You may stay with Grok Bot if your team wants to talk to the same Bot in Slack or Microsoft Teams, or have it join meetings. Its Team Bots keep each person's chat private and let owners review suggested team learnings. Keep a working setup if these conversations are where your team already hands off work.
What you give up
Task Machine's docs do not describe a Bot that joins your meetings or an importer for Grok Bot conversations, skills and routines. Reconnect accounts, rebuild the selected process and check its permissions yourself. Keep the tools you need rather than assuming that moving a workflow replaces them.
There is no trial. Your first payment funds usage, and ordinary unsuccessful work still consumes it. Read Billing before moving frequent routines. You keep 100% of your revenue, Task Machine takes no cut, and never custodies your accounts.
How the switch works
- Save the results you need before deleting anything. Grok Bot's files guide describes saving result cards and moving files to connected storage. Ask each Bot what it remembers, copy the useful guidance, and record each routine's instruction, trigger and timezone. Check its export options for anything else you need to preserve.
- Create your workspace, connect the accounts for one selected job, and upload its source files to the Library. Do not treat a copied Bot configuration as an imported agent.
- Choose a Playbook or rebuild the skill as a Workflow. Give the job a Task owner and acceptance requirements, such as a report that cites every source figure.
- Set autonomy and keep sending, publishing and spending behind review. Test one run with safe inputs, inspect its result, and correct the reusable guidance in Memory.
- Pause the original routine before enabling the replacement's schedule or live writes. Review Grok Bot's access-removal steps for unused logins and connectors. Check what else your subscription covers before cancelling it.
Common questions
What happens to my Bot's data?
Keep original source files and save generated results from Grok Bot. Its Bot guide says deleting a Bot erases conversations, memory, routines and attachments, while shared-computer files and sign-ins can remain. Preserve what you need first, then remove access separately.
How do the costs compare?
Grok Bot billing depends on whether you use The X Subscription or a legacy Cursor account. Task Machine's pricing is usage based, from $29 a month before tax, with no base fee and no trial. Compare the usage consumed by one representative job rather than treating a Bot's weekly allowance as a Task count.
Should I delete my Cursor account when I leave?
Only if you intend to lose that account too. Grok Bot's FAQ says account deletion also deletes your Cursor account and its chat history and settings. Moving one job does not require deleting the account.
Can I choose the model in Task Machine?
Yes. Auto chooses a model for each stage from the task, current model capabilities, pricing and applicable budgets. You can fix a specific model on an agent instead.