TODO for AI
vs 
Make
By Marcell Havlik, founder of TODO for AI · Updated
Visual scenario builder with credit-metered runs and AI agents on every plan. Here is where each one wins, with numbers, and who should pick which.
| Fact | Make | TODO for AI |
|---|---|---|
| Interface | Web | Web, desktop, mobile, CLI, IDE (Zed, JetBrains, VS Code), voice |
| Models | Vendor managed, or bring your own LLM key | Claude, GPT, Gemini, Grok and other supported models |
| Source | Closed | Edge + CLI public |
| Starts at | Free | Free |
Key takeaways
- Models. Make model choice: Vendor managed, or bring your own LLM key. TODO for AI includes Claude, GPT, Gemini and Grok on paid plans. Pick the model for each job; let another review the result.
- Benchmark. TODO for AI scored 91.0% on Terminal-Bench 2.1 with Opus 5.5 (high) (own harness, 81/89 tasks, 2026-10-26; not an official leaderboard submission).
- Price. Make pricing: Free 1,000 credits/month with 2 active scenarios, Core $9, Pro $16, Teams $29 per month at 10,000 credits, Enterprise custom. TODO for AI has a free plan (Claude Sonnet only), then Starter $20, Pro $100 or Ultra $200 a month with the supported multi-vendor catalog.
- Shared business work. TODO for AI: Your whole team and its AI agents, on one board. Shared company context, brand voice and memory. AI working in your connected tools, signed-in browser and machines.
- Included usage. One shared pool of credits, with the cloud VM and browser included. Personal session and weekly limits apply. Credit usage depends on the model; see the pricing page for plan details.
- Who should pick which. Pick Make if the process repeats and is worth drawing once. Pick TODO for AI if Tasks are one-offs you would rather describe than diagram.
Make
TODO for AI
Supported vendorsWhere our product fits
One board for the company’s work.
People decide. Agents do the work.
Your whole team and its AI agents, on one board. Shared company context, brand voice and memory. AI working in your connected tools, signed-in browser and machines.
Chase the invoice. Ship the website update. Prepare the report. Fix the code. Every task keeps its request, contributors and result together, ready for the next colleague or agent to pick up.
Keep Make where it fits. Bring the rest of the company’s backlog here.
Plans and usage limitsWhat Make is, and where it stops
Make is what you pick when Zapier's linear steps stop being enough. The canvas shows branching, iteration and error handling as a diagram, the per-run cost is lower, and AI agents come on every plan including Free. Being able to attach your own LLM key is a genuinely unusual bit of openness in this category.
It is still a builder. Value starts after you have drawn the scenario, which makes it excellent for work that repeats and pointless for the task you would rather describe once. Credits meter each module action, so the elaborate scenarios you were encouraged to build are also the expensive ones, and unused credits expire with the term.
Teams who want Zapier-style automation with more control and a lower per-run cost.
Three reasons Make users look elsewhere
A scenario has to exist before anything runs. For a one-off task, building the diagram costs more than doing the work by hand.
Roughly a credit per module action means the branching, iterating scenarios Make is good at are the ones that drain the pool fastest.
Modules and connectors only. No shell, no file system, no session in your Chrome, so anything without a decent API is out of reach.
Six dimensions that decide it
Make 15/30TODO for AI 28/30How does Make compare to TODO for AI, feature by feature?
| Feature | Make | TODO for AI |
|---|---|---|
Persistent cloud VM A hosted workspace with persistent files, separate from the machines you connect. | No | Yes |
Model choice | Vendor or your own key | Supported models across vendors |
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. | Whatever a module exposes | Yes |
Any CLI as an integration | MCP + HTTP module | 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. Runs remain subject to usage limits. | AI agents, all plans | Configured per task |
Projects for the whole company Engineering, marketing, ops, finance: separate projects and agents, one team and one bill. | Scenarios and folders | Unlimited, shared |
Team roles and usage Pooling is not exclusive to TODO for AI. A shared budget does not remove personal session or weekly limits. | Seats + credit pool | Shared credits, per-seat limits |
Tool permissions | Basic | Allow, approve, block |
Open runtime | No | Edge + CLI public |
Same ladder, different meter
Credits, roughly one per module action, so a long scenario costs more per run than a short one. Credits expire at the end of the term and scenarios stop when they run out. AI agents are on every plan and draw from the same pool, or you supply your own LLM key.
One shared pool of credits, with the cloud VM and browser included. Personal session and weekly limits apply. Credit usage depends on the model; see the pricing page for plan details.