Switch from OpenHands to Task Machine
OpenHands keeps agent work in Canvas conversations and automations across selected backends. Task Machine gives people and agents shared Tasks with plans, checks and an Inbox for decisions.
Prefer the side-by-side comparison?Why people switch
-
Separate identities cost extra
Free Agent Canvas uses a single user or shared identity. Self-hosted Teams adds separate identities and role-based access for $500 a month for up to 10 users, plus $50 a month per additional seat.
-
Script logs can disappear
On Cloud backends, script automation logs become unavailable when the run's sandbox is deleted. OpenHands says to open the logs while the run is in progress.
-
Some webhooks need relays
Custom event sources cannot directly verify the signature formats used by Stripe, Slack, Twilio or Standard Webhooks. The documented connection needs a relay that checks and re-signs each request.
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 OpenHands | In Task Machine |
|---|---|---|
| Work record |
In OpenHands
A conversation is one agent session on the active backend, with its own messages, tool calls, file changes and selected agent profile. |
In Task Machine
Every job is a Task that a person or an agent owns. Its plan, discussion, decisions, runs and history stay together when responsibility changes. |
| Recurring work |
In OpenHands
Automations use schedules, webhooks or events. The Automate view shows the prompt or script, trigger configuration and recent run history on the active backend. |
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 OpenHands
The SDK offers confirmation policies for all actions, risky actions or none. A custom handler can collect pending actions and reject them with feedback. |
In Task Machine
Decisions arrive in your Inbox with their context. Set each agent action to Ask first or Automatic, and add Human approval steps before actions such as sending a report. |
| Models |
In OpenHands
Canvas accepts provider keys, local compatible servers and subscription logins through an ACP agent on the backend's machine. |
In Task Machine
Auto chooses a model for each stage from the task, model capabilities, pricing and applicable budgets. You can choose a fixed model instead. |
| Execution |
In OpenHands
Canvas connects to backends on your machine, in Docker, on a virtual machine or in managed OpenHands Cloud. The backend determines which workspace the agent can access. |
In Task Machine
Run agents in Managed Cloud with nothing to install, or connect a Local Worker for files, tools and accounts on a computer you control. Choose where each agent runs. |
| Code review |
In OpenHands
The software factory uses an independent reviewer that cannot push code. Its watchdog merges only with passing acceptance statuses for the current revision and passing Actions runs when present. |
In Task Machine
Internal code review checks enabled repository rules. Rule discovery proposes rules screened against violating and valid examples, and pull-request approval is tied to the exact commit. |
| Pricing |
In OpenHands
Canvas is free to self-host with your own model key. Teams has a 5,000-session monthly cap and Enterprise has custom pricing. Cloud separately uses credits for OpenHands-provider usage. |
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. OpenHands is named only to identify it, and there is no relationship between the two companies. Has something changed? Tell us.
You may stay with OpenHands if
You may stay with OpenHands if you want its open-source Canvas to manage different coding agents and backends, or you build applications with its Python SDK. Its goal loop already uses a judge to send missing work back to the agent, so needing output checks alone is not a reason to move.
What you give up
Task Machine's docs do not describe a replacement for OpenHands' Python SDK or an importer for Canvas automation files. Keep custom SDK applications where they run, and rebuild selected jobs as Tasks or Workflows. You will spend time translating prompts, reconnecting tools and testing triggers and review boundaries.
There is no trial. Your first payment funds usage, and unsuccessful attempts can consume it too. Read Billing before moving a busy automation. You keep 100% of your revenue, Task Machine takes no cut and never custodies your accounts.
How the switch works
- In Canvas, export each automation as JSON. Save the Activity Log as CSV or JSON, and export important conversations as Markdown or HTML. On Cloud, check that the transcript contains the history you need because exports use the events currently loaded. Preserve repository branches and uncommitted work separately.
- Create your workspace, connect the repository and add service Connectors. Keep credentials in the Vault. Review repository guidance for Task Machine's TAMA.md instructions rather than assuming every Canvas setting transfers.
- Rebuild one automation as a Task or Workflow. Copy its intended outcome, inputs and acceptance checks, then assign an agent. Keep useful transcript extracts in the Library as reference material, not as an imported execution history.
- Choose Supervised autonomy, review the plan and test with copied inputs. Check the output in Run history and keep external writes behind approval while you compare results.
- Set the replacement's schedule and timezone or event trigger. Before enabling live writes, disable the original Canvas automation so both do not act on the same event. Check for work still running before retiring its backend.
Common questions
Can I import my automations and data?
Canvas documents JSON automation exports and Activity Log downloads, plus transcript exports. Keep them as an archive. Task Machine's docs do not describe importing a Canvas definition, so rebuild the process and save selected reference material in the Library.
How do the costs compare?
Free Canvas requires your own model key and self-hosting. OpenHands Cloud uses credits for its provider. Task Machine's pricing starts at $29 a month before tax, with the whole payment available as shared workspace usage and no base fee or trial. Compare a representative job, including your existing model and hosting bills, rather than treating sessions as Tasks.
Can Task Machine host my OpenHands agent?
Task Machine is not a worker host for OpenHands or for the third-party coding agents used in Canvas. Configure a Task Machine agent on Managed Cloud or a Local Worker, and keep any SDK application you still need separate.
Must I move all my coding work?
Move one recurring job first. Leave custom SDK applications in place and use Tasks for work you want people and agents to hand between them with a shared plan, decisions and result.