Switch from Roma to Task Machine
Roma keeps people and connected agents on shared task lists. Task Machine gives agent work reviewed plans, workflow checks and an Inbox for decisions.
Prefer the side-by-side comparison?Why people switch
-
Custom tools on schedules
Roma automations can use custom Model Context Protocol servers' reading tools only. Tools that change or remove something are available in chat, where you can approve each call or allow it always.
-
Repository work needs tests
Roma's GitHub Operator writes text files through pull requests but runs no builds or tests. This describes the built-in Operator, not the external agents you connect.
-
Browser runs have limits
Roma's Operator browser is in beta with a limit of 20 runs over the last 24 hours across chats, tasks and automations. A sign-in requiring a second verification step ends the run in this beta.
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 Roma | In Task Machine |
|---|---|---|
| Tasks |
In Roma
Assigned to names a person on a shared list. Delegate hands the task to the Operator or one of your own connected agents, and members discuss the work in its shared conversation. |
In Task Machine
A person or an agent owns each Task. Its plan, discussion, decisions, runs and history stay together, so you can steer a job such as a client report on the same record. |
| Recurring work |
In Roma
Automations run on demand, on a schedule in your timezone or after completion. Results land in chat, and the automation's page keeps each run's transcript. |
In Task Machine
Start a Task or Workflow once or on a repeat in your timezone. A recurring job keeps one stable root Task, with each occurrence's own status and history. |
| Approval |
In Roma
Operator actions have Always allow, Ask first or Never settings. Ask first shows the exact action on a card in chat and waits for your approval. |
In Task Machine
Decisions arrive in your Inbox with context. Set each agent's actions to Ask first or Automatic, and place a Human approval step before sending a report or publishing a document. |
| Memory |
In Roma
Roma builds a personal journal and profile from tasks, notes, conversations and connected apps. You can read and correct the summary on its Memory page. |
In Task Machine
Agents carry lessons such as accepted examples into later work. Memory is kept per agent, project, goal, team and workspace, and you can read, correct and restore notes. |
| Connections |
In Roma
Add a custom remote Model Context Protocol server in Settings or through chat. Once connected, its tools are available to the Operator across your devices. |
In Task Machine
Install services from the Connectors catalog or add a custom connection through an API, a command-line tool or Model Context Protocol. Assign each connection to the agents that need it. |
| Pricing |
In Roma
The US App Store lists the iPhone download as Free. A monthly service price and included model usage remain unverified, and the pricing address displays the product homepage. |
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. Roma is named only to identify it, and there is no relationship between the two companies. Has something changed? Tell us.
You may stay with Roma if
You may stay with Roma if you want your team's existing agents to work on shared lists. Its Mac and iPhone clients add capture through a global shortcut, hold-to-talk, the Action Button and the share sheet. You can edit lists offline and sync later, although the Operator needs the network.
What you give up
Task Machine's docs do not describe Roma's native Mac capture controls, an iPhone Action Button integration or offline list editing. Its docs also do not describe importing Roma conversations, logs, automations or memory as working records. Reconnecting accounts, rebuilding selected jobs and checking who can read the copied material takes time.
There is no trial. Your first payment funds usage, so budget for rebuilding and testing before moving live work.
How the switch works
- Before changing the old setup, keep a copy of the selected lists, task bodies, conversations and automation instructions. Check Roma's export options. Its REST API documents reads for lists, items, messages and logs, which can help you make an archive. This is not an automatic migration.
- Create your workspace, choose a Project for the first job and connect its accounts. Save reference files in the Library. Copy only material the new workspace's members should see.
- Rebuild one job as a Task or a Workflow. For a weekly report, name the input sources, required sections and review boundary, then add a verifier to check the result against those requirements.
- Choose Supervised autonomy for the first cycles and keep an explicit approval before sending or publishing. Test on copied inputs and compare the output before enabling external changes.
- Pause the Roma automation and stop any connected agent's old job before enabling the replacement's schedule. Check the timezone and next occurrence so the same report is not sent twice.
Common questions
Can I bring my Roma data?
Keep an archive before moving. Roma's API reference documents reading list items with Markdown bodies, plus messages and logs. Task Machine's docs do not describe a Roma importer, so rebuild selected Tasks and keep reference material in the Library.
How do the costs compare?
Roma's US App Store listing establishes a free iPhone download, not the cost of ongoing agent work. Task Machine's pricing starts at $29 a month before tax, with the whole payment available as workspace usage and no base fee or trial. Compare a representative job rather than assuming the billing units match. You keep 100% of your revenue, Task Machine takes no cut and never custodies your accounts.
Should every shared list move?
Move the job that needs explicit checks first. Keep lists in Roma when its existing-agent connections or capture tools fit your team, and avoid giving both systems permission to perform the same live action.
Where do repeated instructions go?
Put source material and longer instructions in Library documents. Rebuild the process in a Workflow, and add accepted examples or recurring corrections to Memory. An archived conversation is reference material, not a recreated approval or schedule.