TODO for AI
vs 
GitHub Copilot
By Marcell Havlik, founder of TODO for AI · Updated
GitHub's coding agent: completions in the editor, a cloud agent that takes an issue and opens a pull request. Here is where each one wins, with numbers, and who should pick which.
| Fact | GitHub Copilot | TODO for AI |
|---|---|---|
| Interface | IDE, GitHub.com, CLI | Web, desktop, mobile, CLI, IDE (Zed, JetBrains, VS Code), voice |
| Models | OpenAI, Anthropic, Google, xAI, more | Claude, GPT, Gemini, Grok and other supported models |
| Source | Closed | Edge + CLI public |
| Starts at | Free | Free |
Key takeaways
- Models. GitHub Copilot model choice: OpenAI, Anthropic, Google, xAI, more. 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. GitHub Copilot pricing: Free tier, Pro $10, Pro+ $39, Max $100 per month. Business and Enterprise seats add org controls. Business $19 and Enterprise $39 per seat include pooled AI Credits; agent usage is token-metered. 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 GitHub Copilot if your work is GitHub issues and pull requests. Pick TODO for AI if a lot of your backlog never becomes a pull request.
GitHub Copilot
OpenAI, Anthropic, Google, xAI, more
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 GitHub Copilot where it fits. Bring the rest of the company’s backlog here.
Plans and usage limitsWhat GitHub Copilot is, and where it stops
Copilot is the default coding agent by distribution. It completes in the editor, reviews pull requests, and the cloud agent picks up an issue, works on GitHub's runners and opens a PR. The model picker is the most open of any coding agent here: OpenAI, Anthropic, Google, xAI, Moonshot and Microsoft models, with Claude Code and Codex available as third-party agents on the same surface.
The shape is the constraint. Copilot works where GitHub works: repositories, issues, pull requests, Actions. Anything that is not a diff has no home. Copilot CLI does run in your terminal with per-command approval, but the agent that works unattended runs on GitHub's runners, and token-metered agent work can exceed the included pool.
Teams whose work lives on GitHub and who want agents attached to issues and pull requests.
Three reasons GitHub Copilot users look elsewhere
The unit of work is a diff, tracked as an issue on a repository. An invoice to chase, a campaign to launch or an inbox to triage has no shape in Copilot.
Copilot CLI runs locally, but the agent that works unattended does so on GitHub's runners, on a clone of the repo. It reaches neither your servers nor your logged-in browser.
Completions are unlimited, agent work is not. AI Credits are consumed at model token rates. Admins can allow extra paid usage or cap spending when the pool runs out.
Six dimensions that decide it
GitHub Copilot 16/30TODO for AI 28/30How does GitHub Copilot compare to TODO for AI, feature by feature?
| Feature | GitHub Copilot | TODO for AI |
|---|---|---|
Persistent cloud VM A hosted workspace with persistent files, separate from the machines you connect. | GitHub runners per task | Yes |
Model choice | OpenAI, Anthropic, Google, xAI | 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. | Code and pull requests | Yes |
Any CLI as an integration | CLI locally, 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. | Yes, issues and pull requests | Yes |
Many agents, each configured Each agent gets its own model, prompt, tools and permissions. Runs remain subject to usage limits. | Coding agent + custom agents | Configured per task |
Projects for the whole company Engineering, marketing, ops, finance: separate projects and agents, one team and one bill. | Repos and issues | 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. | Business / Enterprise, pooled AI Credits | Shared credits, per-seat limits |
Tool permissions | Repo scopes + command approval | Allow, approve, block |
Open runtime | No | Edge + CLI public |
Same ladder, different meter
Completions are unlimited on paid plans. Agent work spends AI Credits at published model token rates. Business includes 1,900 and Enterprise 3,900 credits per seat, pooled across the organization; 1 credit is $0.01. Additional usage is controlled by admin budgets.
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.