Cursor (legacy) vs Claude Pro (Claude Code): limits compared
| Cursor (legacy) | Claude Pro (Claude Code) | |
|---|---|---|
| Plan | Pro | Pro |
| Status | legacy | current |
| Price $/mo | 20 | 20 |
| Metered in | Dollars of usage (two monthly pools) | Five-hour and weekly limits |
| Stated limits | Two monthly pools: Cursor Models and Other Models (third-party at provider prices); on-demand usage for extra requests | Claude Code included; at least 5x Free per five-hour session, with weekly limits shared with chat; extra use at API rates or bundles ($45 buys $50) |
| Resets | Monthly (billing cycle); no rollover | Every 5 hours + weekly |
Cursor (legacy) user reports
- Anecdote “Cursor (auto) - 60M tokens / month ($20)” (User estimate from ccusage/Cursor usage stats) source
- Anecdote “Composer with Opus burns through the $20 plan in days.” source
- Anecdote “Combined all 3 tasks Cursor used 2% of weekly and the xAI used 8% but took longer on everything and seemed to do more work.” (u/okdesign, side-by-side test of the $20 Cursor plan vs the $30 xAI plan, read from each plan's usage meter (added 2026-10-17)) source
Claude Pro (Claude Code) user reports
- Anecdote “Opus - 10M tokens / 5hr; Sonnet - 20M tokens / 5hr; Haiku - 40M tokens / 5hr” (User estimate (ccusage)) source
- Anecdote “I can easily run out of tokens with 2 or 3 feature requests or debugging sessions.” source
- Anecdote “at 20$ you get around 1.3 B tokens using opsy 5.5” (u/Machine2024, Opus 5.5 medium only, measured at 30M/50M/100M checkpoints with ~85% cache; another commenter notes most of that is likely cached reads (added 2026-10-17)) source
Units differ between vendors and aren't directly comparable.