Comparison · Linear

TODO for AI
vs Linear

By Marcell Havlik, founder of TODO for AI · Updated

The issue tracker engineering teams like, with its own Linear Agent and coding sessions in a Linear sandbox. Here is where each one wins, with numbers, and who should pick which.

FactLinearTODO for AI
InterfaceWeb, desktop, mobileWeb, desktop, mobile, CLI, IDE (Zed, JetBrains, VS Code), voice
ModelsLinear Agent: Claude, GPT or GLM, picked per workspace; delegated agents bring their ownClaude, GPT, Gemini, Grok and other supported models
SourceClosedEdge + CLI public
Starts atFreeFree
Facts verified 2026-09-30. Pricing is public list price.

Key takeaways

  • Models. Linear model choice: Linear Agent: Claude, GPT or GLM, picked per workspace; delegated agents bring their own. 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. Linear pricing: Free, Basic $10, Business $16 per user per month billed yearly, Enterprise custom. Coding sessions draw AI credits: model tokens at provider rates plus $0.25 per 20 minutes of sandbox. 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 Linear if your work is engineering issues and cycles, and you want the best tracker for them. Pick TODO for AI if the work on your board is not only code.
Multi-vendor
models, vs linear agent: claude, gpt or glm, picked per workspace; delegated agents bring their own
Your machines
PC, cloud VM, real Chrome
Any CLI
is an integration, not just MCP
Free
from, vs Free
Architecture at a glance
Linear
Models
AnthropicOpenAIGoogleLinear Agent: Claude, GPT or GLM, picked per workspace; delegated agents bring their own
Runs in
Web, desktop, mobile
Where it lives
Linear sandbox for coding sessions
Produces
Tasks
Docs
Engineering first, MCP beyond
SEO
Email
Ads
TODO for AI
Models
AnthropicOpenAIGooglexAIDeepSeekSupported vendors
Cross-vendor review
Runs in
Your PC
Cloud VM
Real Chrome
Your IDE
Voice
Where it lives
Always-on cloud VM · vault · your logins
Produces
Code
SEO
Email
Ads
Social
CRM
Struck-through outputs are outside Linear's scope. TODO for AI runs the same models plus the rest, from a machine that stays on.
Positioning

Where our product fits

Where the work lives

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 Linear where it fits. Bring the rest of the company’s backlog here.

Plans and usage limits
Context

What Linear is, and where it stops

Linear is the closest thing to what we are building, from the opposite direction. It already has the thing the agent vendors do not: a real shared board, where a teammate and an agent can hold the same item, where state is queued, started, blocked and done, and where everyone can see it. It now has its own worker too. Linear Agent answers in chat, in comments and in Slack, creates and updates issues, runs Skills and scheduled Loops, reaches other tools over MCP, and starts coding sessions in a Linear-hosted sandbox that installs the toolchain, tests the app in a browser and opens the PR. Admins pick Claude, GPT or GLM for the workspace.

The shape is still product and engineering. The sandbox works on a GitHub repo, the browser inside it is for testing your app, and anything else goes through whatever MCP connections exist. There is no shell on your own machines, no session in your logged-in Chrome, and the model is one workspace setting rather than a choice per agent.

Engineering teams who want issues, cycles and coding agents on one board.
Why people switch

Three reasons Linear users look elsewhere

01
Built for issues that end in a PR

Linear Agent can reach other tools over MCP, but the sandbox, the browser and the workflow are shaped around a repo. Invoices, outreach and ad accounts have no natural home there.

02
Their sandbox, not your machine

Coding sessions run in Linear's managed sandbox. Linear never gets a shell on your box or a session in your Chrome, so a tool behind your logins without a connector goes back to a human.

03
One model per workspace

Admins choose the model for coding sessions across the workspace. TODO for AI sets the model per agent, so triage can run on a cheap model and the hard part on a strong one.

Scores

Six dimensions that decide it

Six dimensions, 0 to 5
Linear 17/30TODO for AI 28/30
Model freedom3 · 5 /5
Which vendors and models you can run
Long-running work3 · 5 /5
Persistent machine, scheduling, parallel tasks
Beyond code2 · 5 /5
Marketing, ops, browser, email, not only repos
Openness1 · 4 /5
Source available, self-host, extend
Team & permissions5 · 5 /5
Roles, pooled usage, tool approvals
Cost predictability3 · 4 /5
Included usage, limits and additional charges
Feature by feature

How does Linear compare to TODO for AI, feature by feature?

TODO for AI vs Linear, feature by feature. Verified 2026-09-30.
FeatureLinearTODO for AI
Persistent cloud VM
A hosted workspace with persistent files, separate from the machines you connect.
Linear sandbox for coding sessions
Yes
Model choice
Claude, GPT, GLM per workspace
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.
Sandbox browser for testing, not your session
Yes
Business tasks, not only code
SEO, email, ads, social, CRM via CLI tools.
Engineering first, MCP beyond
Yes
Any CLI as an integration
MCP + Agent API
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, for engineering issues
Yes
Many agents, each configured
Each agent gets its own model, prompt, tools and permissions. Runs remain subject to usage limits.
Linear Agent + 30+ delegated
Configured per task
Projects for the whole company
Engineering, marketing, ops, finance: separate projects and agents, one team and one bill.
Teams and projects
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.
Per seat + AI credits
Shared credits, per-seat limits
Tool permissions
OAuth scopes
Allow, approve, block
Open runtime
No
Edge + CLI public
Pricing

Same ladder, different meter

TierLinearTODO for AI
EntryFreeFree (Sonnet only), or Starter $20
MidBasic $10 per userPro $100
TopBusiness $16 per userUltra $200
TeamBusiness $16 per user, Enterprise custom$30 standard / $120 premium per seat, min 2 seats
Linear · what it meters

Seats, plus AI credits for coding sessions and Loops (tokens at provider rates, sandbox $0.25 per 20 minutes). Delegated agents such as Devin or Cursor bill on their own plan on top.

TODO for AI · what it meters

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.

USD per month, monthly billing, public list prices as of 2026-09-30.
Verdict

Bottom line

Our take
Linear is excellent and we are not trying to replace your issue tracker. The difference is what an item can be and where it gets done: in Linear it is mostly engineering, worked in Linear's sandbox, in TODO for AI it is any task, worked by an agent you configured, on machines you own and in your own Chrome, with the rest of the company on the same board.
FAQ

Common questions

What do AI-native startups use instead of Linear?
Most keep Linear for engineering issues and add a coding agent such as Claude Code, Codex or Cursor that picks issues up. The ones whose board also holds sales, ops and content move that work to a board where an agent does each task, such as TODO for AI, and keep Linear only for the code.
Is TODO for AI a Linear alternative?
Only if your board holds more than engineering. Linear is the better issue tracker. TODO for AI is a board where any task, code or not, gets done by an agent with a shell on your machines. Plenty of teams keep both and let TODO for AI take the work that never becomes an issue.
Can Linear agents do non-coding work?
Some. Linear Agent summarizes, drafts updates, manages issues and reaches other tools through MCP connections. It cannot use your logged-in browser or your own machines, so anything behind your logins without an MCP server goes back to a person.
Does Linear run agents on my machine?
No. Linear Agent's coding sessions run in a Linear-hosted sandbox. You can open an issue in Claude Code or Cursor locally, which runs through that tool. TODO for AI connects your PC with a ~300 KB bridge and runs agents there directly.
Which is cheaper?
Linear is $10 to $16 per seat for the tracker, and agent work is billed on top as AI credits. TODO for AI Standard seats cost $30/month and add 30 credits to a shared pool. Minimum two seats. Credit usage depends on the model and personal limits apply, so neither the sticker price nor the nominal pool establishes which is cheaper.