Cursor Hobby Limited Agent: when indies should buy Pro

After you install Cursor, the first hard question is rarely whether the editor feels nice. It is when Hobby’s Agent allowance runs out and whether Pro at $20 per month is the rational next buy. This page does not reopen Cursor versus VS Code or Claude Code. It freezes what cursor.com/pricing showed on 2026-10-01: what Hobby includes, what Pro adds, and which observable signals justify upgrading. Re-open the pricing page before you pay; copy changes.

What Hobby actually includes

The free tier is labeled Hobby for tinkering. The card states there is no credit card required, Limited Agent requests, and Access to Composer. You can use Composer on the free plan for edit-and-complete workflows, but Agent is explicitly limited rather than unlimited. The same card does not publish a single public integer for daily or monthly Agent requests. Do not invent a hard quota the vendor did not print; treat in-product usage cues and the live pricing card as the source of truth.

Hobby is enough to test whether Cursor belongs in your mainline: clone a repo, land small features, use Composer to tighten patches. If you only touch a docs site on weekends, Limited Agent often lasts. Once Agent becomes the default path for daily shipping—scoping work, editing many files, running checks, drafting notes—you will hit usage friction more often, and that is when Pro has a fair comparison point.

What Pro buys beyond Hobby

Individual Pro maps to $20 per month on the Offer markup and pricing card (taxes extra per the FAQ). Relative to Hobby, the card highlights Extended limits on Agent, Generous limits for Grok, Access to frontier models, Grok Bot access, and Bugbot on usage-based billing. The FAQ also states every plan includes model usage, with on-demand usage after the included amount. Pro+ and Ultra target heavier Agent users; Teams targets collaboration and admin controls. For a solo indie, the first paid door is usually Pro, not a team SKU.

Translate the extras into tasks: you are paying for steadier Agent quota, wider model access, and Grok-related capabilities—not for a different icon. If your real blocker is SSO, pooled usage, or org policy, look at Teams or Enterprise instead of expecting Pro to solve org problems.

Signals that Hobby should step aside

Prefer two consecutive weeks of these observables: Agent usage warnings interrupt shipping so often that you fall back to pure manual edits or other tools; you need the frontier models named on the pricing path and Hobby clearly cannot sustain them; Grok or Grok Bot is part of your debug or review loop; you are ready to enable Bugbot-style usage-based billing instead of staying in trial mode. Also upgrade when release work stalls because Agent interruptions force overnight hand edits.

Stay on Hobby if Composer already covers most patches, Agent is occasional help, and you can split complex work into smaller manual steps. Before paying, write one purchase sentence such as “buying Extended Agent limits for a daily Agent main path,” so social screenshots do not drive the subscription.

Spend Hobby quota on the sharp edge

Treat Agent like a budget, not the default for every line. Clear, local edits prefer Composer; cross-module exploration, failure reproduction, and wide renames earn an Agent session. Start each session with target files and a done definition to cut empty loops. Verify locally before asking Agent to expand scope. Every Friday, review which sessions actually moved a release and which were chat. If two weeks of that discipline still hit the wall, Pro has a harder case than “everyone else upgraded.”

Repo hygiene saves requests too. Keep README and contribution notes current; make typecheck and test commands copy-pasteable; write recurring answers into rules or docs instead of re-explaining structure every time. Those habits still save money on Pro because on-demand usage remains.

Keep this separate from toolchain comparisons

Toolvori already publishes Cursor versus VS Code/Copilot and Claude Code comparison pieces. Those answer which toolchain to pick. This tutorial answers only Hobby versus Pro quotas and capability gates. Pin the official card points with an observation date. When someone claims “free is always enough” or “you must buy Ultra now,” open the pricing page and your two-week signal list instead of arguing from memory.

In the first week after paying, wire the Agent main path into a real release flow and check the usage panel to confirm Extended limits removed the old interruptions. If you subscribe and keep typing everything by hand, the plan becomes shelfware. Re-check the live $20 per month Pro price plus billing toggles and tax notes before you confirm checkout.