TODO for AI
vs
OpenHands
By Marcell Havlik, founder of TODO for AI · Updated
Open-source autonomous software agent with a self-hosted or cloud workspace. Here is where each one wins, with numbers, and who should pick which.
| Fact | OpenHands | TODO for AI |
|---|---|---|
| Interface | Web, CLI | Web, desktop, mobile, CLI, IDE (Zed, JetBrains, VS Code), voice |
| Models | Any provider | Any provider: Claude, GPT, Gemini, Grok, Ollama |
| Source | Open | Edge + CLI public |
| Starts at | Free (self-host) | Free |
Key takeaways
- Models. OpenHands model choice: Any provider. TODO for AI runs any provider, Claude, GPT, Gemini, Grok or a local Ollama model, on one plan, and one model can review another's work.
- Benchmark. TODO for AI scored 89.9% on Terminal-Bench 2.1 with Opus 5.5 (high) (own harness, 80/89 tasks, 2026-10-08; not an official leaderboard submission).
- Price. OpenHands pricing: MIT self-host. Cloud is credit based. TODO for AI has a free plan (Claude Sonnet only), then Starter $20, Pro $100 or Ultra $200 a month with any provider included.
- Where the work happens. OpenHands gets one task done in a sandbox per task. TODO for AI is one board your team and agents work through together, on your own PC, a cloud VM and your logged-in Chrome.
- Who should pick which. Pick OpenHands if you must self-host everything. Pick TODO for AI if you want a persistent VM with your real logins, not a fresh sandbox.
TODO for AIWe are not competing for the same job
OpenHands gets the task done.
TODO for AI organises the whole company’s work.
OpenHands answers one question: how do I get this task done, in a sandbox per task? So do the others — Cursor inside the editor, Claude Code in one person's session, Lindy by asking its assistant.
We answer a different one: where does the work live? One board per project, and a project for each part of the company — engineering, marketing, ops, finance, one per client. Your colleagues work on it. So do your agents, as many as you want to run, each with its own model, tools and permissions. Items carry the people who worked them and the agent that ran them, and the board filters by person, so what the company has in flight is one screen instead of a Slack thread.
That is not a team plan bolted onto an AI tool. It is the product. The agents are how items get closed; the board is what the company runs on.
What OpenHands is, and where it stops
OpenHands is the most serious open-source autonomous coding agent: MIT licensed, multi-model, a sandboxed workspace per task, and a cloud offering if you do not want to host it. It is the closest thing on this list to what TODO for AI does for code.
Where it stops is the edge of the repository. The sandbox is fresh per task rather than a persistent machine with your logins, there is no real-browser automation, and the integrations are aimed at software engineering rather than the rest of the business. Self-hosting is real ops work.
Teams that want an open, self-hosted autonomous coding agent.
Three reasons OpenHands users look elsewhere
Each task gets a clean container. Your Chrome session, your CLI logins and your half-done state do not live there.
Excellent for pull requests, silent on marketing, email, ads and ops.
Running it well means running it yourself.
Six dimensions that decide it
How does OpenHands compare to TODO for AI, feature by feature?
| Feature | ||
|---|---|---|
Persistent cloud VM An always-on machine. Files, logins and sessions survive between runs. | Sandbox per task | Yes |
Model choice | Any provider | Any provider |
Cross-vendor review Review GPT output with Claude, or the other way around. | No | Yes |
Drives your real browser Browser extension (Chrome, Firefox) plus cloud browsers. | No | Yes |
Business tasks, not only code SEO, email, ads, social, CRM via CLI tools. | No | Yes |
Any CLI as an integration | MCP | Any binary |
Voice control | No | Yes |
People and agents on one board Colleagues and agents work the same list. Items show who contributed and which agent ran them; filter the board by person. | No | Yes |
Many agents, each configured Each agent gets its own model, prompt, tools and permissions. Pick which one takes an item. | Microagents | Unlimited, per task |
Projects for the whole company Engineering, marketing, ops, finance: separate projects and agents, one team and one bill. | Repos | Unlimited, shared |
Team roles, pooled usage | Cloud plans | Roles + pooled |
Tool permissions | Basic | Allow, approve, block |
Open runtime | Yes | Edge + CLI public |
What it costs
MIT self-host. Cloud is credit based.
Hobby free (Sonnet only), Starter $20, Pro $100, Ultra $200. Paid plans include any model provider.