Cursor review
Written by a competitor: we build TODO for AI. What that means for this review.
The best AI editor available, and still the fastest way to write code with a model at your side. Its limits are the limits of a repo-shaped tool, not of an editor that cannot leave your screen.
Rated as an AI code editor, the job it was actually built for. Reviewed against Pro, Pro+ and Ultra plans as priced in September 2026.
Who is writing this
How we reviewed it
- —Hands-on use of Cursor on a large TypeScript and Python monorepo through August 2026, alongside the CLI agents we build. We have not used it daily since, so anything shipped in the last few weeks is not covered here.
- —Pricing, Cloud Agents and browser behaviour read from Cursor's own docs on 17 September 2026, not from third-party summaries.
- —We have not run a controlled benchmark against other editors. Where we say something is fast or accurate, that is a working impression, not a measurement.
What Cursor does well
It predicts the edit you were about to make, across lines and across files, rather than the token you were about to type. It is our favourite feature in any AI tool and the single thing most likely to keep you subscribed. Cursor includes it unlimited on every paid plan.
It is a VS Code fork with import for your extensions, keybindings and settings, so the cost of trying it is close to zero. It lags upstream VS Code by a version or two and some UI differs, but that low switching cost is a large part of why it won the category.
Claude, GPT, Gemini and Cursor's own Composer, switchable per request. You are not locked to one lab's idea of a good model, which matters more each time the frontier moves.
Cursor runs agents in its own isolated VMs that, in its words, "do not require your local machine to be connected to the internet". They clone the repo, work on a branch and open a merge-ready PR. Anyone still saying Cursor stops when you close the laptop has not looked recently.
What frustrates
In June 2025 Cursor replaced 500 monthly requests with a pool of API-priced credit, and described it in a way that led people to believe far more usage was included than was. They apologised publicly, offered refunds for unexpected charges in the affected window, and rewrote the docs. Credit where it is due: that is a better response than most vendors manage. The two-pool model it left behind still takes a careful read.
Source: Cursor, "Clarifying our pricing", July 2025Unlimited tab completions come with every paid plan. Agent usage does not: included usage is split into a Cursor-models pool and an other-models pool, and Cursor is explicit that "all Auto modes bill at the list price of the model each request is routed to". Auto picks the model for you, it does not stop the meter. Your model choice, not your seat, decides how fast the month burns.
Source: Cursor pricing docs, September 2026Our experience through August 2026, not a measurement: on our monorepo, foreground agent sessions working through a multi-file change tended to lose the thread of earlier decisions and produce edits that did not match the conventions around them. Review caught it and it was still faster than doing it by hand, but we have not tested whether this happens more in Cursor than in other coding agents, and we have not put the same work through Cloud Agents at length.
Cloud Agents start from a connected repo and finish at a pull request. The browser tool exists so the agent can check the app it just changed — navigate, click, screenshot, read the console. Both are good. Both assume the unit of work is a code change. If the task is answering an inbox, updating a CRM or running an ad account, there is no branch to open and no PR to merge, and that is a deliberate scope decision rather than a gap.
Source: Cursor Cloud Agent docs, September 2026Pricing, honestly
Pro $20, Pro+ $60, Ultra $200 per month. Teams starts at $40 per user per month, with Teams Premium at $120 and Enterprise custom.
Unlimited tab completions on every paid plan. Agent usage is not unlimited: it draws on an included Cursor-models pool and an other-models pool that reset with your billing cycle, and Auto bills at the list price of whichever model it routes to.
Third-party models bill at the provider's API rates rather than a marked-up per-request price, which is more honest than it is usually given credit for. On Teams and Enterprise a Cursor Token Rate of $0.25 per million tokens applies on top, including on BYOK usage.
The unpredictability is inherent to token pricing, not a margin grab. But it does mean the invoice depends on which model you reached for, so the plan you need is a function of your habits rather than your headcount.
Who should buy it
- You write code most days and want the best assistance available while you type
- You live in VS Code and want to keep your setup
- You want to switch models per task without switching tools
- Your delegated work is repository work that ends in a pull request
- Most of your week is not source code
- You want one predictable number on the invoice regardless of which model ran
- You need work that ends somewhere other than a branch: an inbox, a CRM, an ad account