Cursor

What it is

Cursor is a code editor with AI built into the center of it rather than bolted on the side. Two things do the heavy lifting. The first is Tab, an in-house autocomplete model that predicts your next action and fires it inline at high speed. The second is Composer, an agent that edits across many files at once, so a change that touches your whole project becomes a single instruction instead of an afternoon of manual edits.

Around those two it does the rest of what you’d expect from a modern AI editor: it indexes your codebase for context, it lets you pick which frontier model answers each request, and its agents can run autonomously to build, test, and demo a feature end to end. As of the June 2026 releases, those agents reach into the terminal, Slack, and GitHub, and can run in the cloud with environment setup under ten minutes.

Who it’s for

This is a tool for daily, professional developers working in real codebases with more than one file in play. That’s exactly where reviewers say it earns its keep. If your work is constant: refactors, migrations, coordinated changes across modules, Composer’s multi-file editing is the reason to switch, and Reddit consensus is blunt about it: cheaper Copilot suits simple autocomplete, while Cursor justifies its price the moment you need codebase-wide work.

It’s a weaker fit if you only want lightweight line completion. At that job the gap over Copilot narrows and the extra cost is harder to justify. It’s also worth a pause if you’re cost-sensitive and prone to heavy bursts, because the usage-based billing rewards predictable use and punishes surprise spikes.

Why it stands out

The autocomplete is the first thing people fall for. G2 reviewers call its speed and accuracy “like telepathy,” independent reviews describe completions as “remarkably accurate” and name it the feature that hooks developers, and Reddit threads say it predicts the next edit rather than the next line and runs roughly twice as fast as Copilot. This is the everyday, always-on win.

Composer is the differentiator. G2 users say it turns large refactors from a nightmare into a joy. A widely-shared r/cursor_ai comment reports handing it a codebase-wide “update all components using the old Button API” instruction and watching it diff every file perfectly, handling 15-plus file refactors autonomously. That’s the capability cheaper assistants don’t have.

Codebase context is the third pillar, and independent reviewers repeatedly call it the killer feature: whole-project indexing of functions, types, patterns, and dependencies, which Reddit developers say lets Cursor coordinate changes across the entire codebase in a way Copilot can’t match. Model flexibility rounds it out. You pick per-chat or per-session from Claude (Sonnet and Opus), GPT, o1, Gemini, and Cursor’s own model, and reviewers consistently rate that choice a strength against Copilot’s GitHub-tied approach.

Pricing in plain language

There’s a free tier, and it’s a real one. Hobby costs nothing, needs no credit card, and gives you limited Tab completions and limited Agent requests. It’s enough to feel how the editor works before you spend anything.

The plan most people land on is Individual at $20 a month. That buys extended Agent limits, access to frontier models, MCPs, skills, hooks, cloud agents, and Bugbot. Independent reviewers call this tier worth it for daily developers, and that matches the Reddit consensus: $20 is justified once you actually use Composer’s multi-file capability.

Teams is $40 per user per month and adds the things a group needs: centralized billing and admin, agentic code reviews with Bugbot, shared team context, usage analytics, team-wide privacy mode, and SAML/OIDC SSO. Enterprise is custom-priced with pooled usage, SCIM, access controls, and audit logs.

Here’s the part to read carefully. Every plan includes a set amount of model usage, and you’re billed on demand beyond it. That credit model is the loudest complaint in every review I read. The 2025 switch from fixed requests to usage-based credits caught people off guard, G2 reviewers reported surprise overages, and one independent review estimated effective monthly requests dropped from around 500 to about 225. The fix is unglamorous but it works: watch the usage dashboard. The tool is worth it, but only if the bill stays predictable, and that’s on you to manage.

Limitations

The billing change is the headline weakness, and it’s as much about communication as cost. The credit system is fine once you understand it, but reviewers felt blindsided by the rollout and by the lower effective request volume, and that resentment shows up across G2, Reddit, and independent reviews alike.

The AI isn’t infallible. Reviewers report Cursor generating inaccurate code that needs manual correction, and some note misplaced edits or unreliable cross-file changes in harder contexts. Composer is remarkable, but you still review what it produces.

Context isn’t permanent either. Reviewers describe the codebase understanding forgetting after long breaks and degrading on large or long-running projects, and several flag that Cursor is resource-intensive and slower on bigger codebases. None of this sinks the tool. It just means the magic has edges, and they show up most on the largest, longest jobs.

The bottom line

If you write code for a living and your work lives across many files, Cursor is the one to use. The Tab autocomplete is the best in the category, Composer does multi-file work that cheaper assistants simply can’t, and the whole-codebase context is the feature that turns it from a nicer editor into a genuinely faster way to work. Roughly 4.7/5 on G2 and the top spot among independent reviewers is not an accident.

Go in with your eyes open on billing. Start on the free Hobby tier, move to the $20 Individual plan when Composer earns it, and keep an eye on the usage dashboard so a heavy week doesn’t become a surprise invoice. Do that, and Cursor is the easiest recommendation in AI coding right now.