
Honestly the context-awareness is what sold me. Most autocomplete tools just guess based on the current file, but Cursor actually indexes the whole repo, so suggestions feel like they come from someone who's read the code, not just skimmed it. Since it's built on VS Code, I didn't have to relearn anything — my keybindings, extensions, settings, all of it just worked from day one, which honestly saved me a whole afternoon of setup pain.
The Composer/Agent stuff is where it really shines though. I'm currently building a React frontend for a foundation that's wired into Zoho CRM, Catalyst, Analytics, and their Zia agents, so a lot of my day is spent stitching together custom API wrappers, type definitions for CRM record shapes, and handling responses coming back from Catalyst functions. That kind of glue code used to be tedious — touch a schema, then remember to update the Catalyst function, then the API call, then the component consuming it. Cursor tracks that chain across files pretty reliably now, so I just describe the change and it handles most of the ripple effect. Being able to flip between Claude 3.5 Sonnet and GPT-4o depending on what I'm doing (quick edits vs. gnarlier logic) has also been a nice bonus I didn't expect to lean on as much as I do. Review collected by and hosted on G2.com.
If your repo is on the bigger side, the local indexing can chew through RAM and CPU more than you'd like — I've had my fans kick on just from it indexing in the background. Premium fast requests also get rate-limited during busy hours on the Pro plan, so occasionally I'm stuck in the standard queue or reaching for my own API key to get around it. And for anything outside typical web-stack territory — in my case some of the more niche Catalyst/ Zoho-specific configs — it'll sometimes confidently hallucinate something that looks right but isn't, so I still double-check that stuff by hand rather than trusting it blindly. Review collected by and hosted on G2.com.