Cursor

Overview

Freshness note: AI products change rapidly. This profile is a point-in-time snapshot last verified on July 6, 2026.

Cursor is still one of the clearest expressions of the “AI-first IDE” idea: a VS Code-style editor where autocomplete, chat, repo rules, cloud agents, review flows, and agent management live in the same surface. The late-June 2026 Cursor cycle keeps widening that surface. Cursor is no longer just selling a better editor; it is selling an engineering agent environment that can start from the IDE, Jira, background cloud work, scheduled automations, mobile sessions, team marketplaces, browser or canvas Design Mode, SDK agents, and review workflows.

Key Features

Cursor’s current product surface highlights what matters most in daily use: agent capacity, tab completions, cloud agents, access to frontier models, MCPs, skills, hooks, and team-level sharing of chats, commands, and rules. That is a good proxy for how the product is actually used. Day to day, the value comes from staying in the editor while switching between narrow tasks like inline rewrites and broader tasks like planning and applying a multi-file change set.

The product is also better understood now as a usage-routed shell around multiple top-tier models rather than a single-assistant experience. Cursor’s current pricing docs frame Pro, Pro+, and Ultra around different usage levels across OpenAI, Claude, and Gemini models. Cloud agents remain a meaningful differentiator because they let you hand off longer-running work to a remote development environment while staying in the main editor flow.

The latest agent updates matter for teams. Cursor Automations now sit inside the Agents Window as well as the web app, and they can run with multiple attached repos or no repo at all. Cursor in Jira lets teams assign a work item to Cursor or mention @Cursor in a comment to start a cloud agent, with the finished task linked back to a pull request. The June 30 team-marketplace update lets admins configure Team MCP servers once and distribute approved integrations across cloud agents, the Agents Window, IDE, and CLI. Bugbot remains Cursor’s PR review product, with project-specific .cursor/BUGBOT.md rules, GitHub integration, analytics, and a separate usage surface.

Cursor 3.9 adds an iOS public beta for paid plans, so users can launch and manage cloud agents from mobile, use voice input, track Live Activities, review artifacts and diffs, and continue directing a local agent through Remote Control when team policy allows it. Cursor also added a Customize page for plugins, skills, MCPs, subagents, rules, commands, and hooks at user, team, or workspace level.

Strengths

Cursor is very good at keeping coding flow intact. You can move from autocomplete to chat to agent review without switching context or changing tools. For teams already comfortable with VS Code ergonomics, adoption is usually fast because the main change is workflow discipline, not editor retraining.

It is also strong for repetitive-but-real work: consistent refactors, test updates, boilerplate expansion, framework migrations, and code review prep. Cloud agents are especially useful when you want long-running tasks to keep moving while you stay in the main editor. The newer cloud environment setup and /in-cloud subagent flow also make it easier to isolate parallel work without tying up the local workspace.

The Jira and automation updates make Cursor more useful outside the moment of active coding. A ticket can become an agent session, and recurring operational work can become a managed automation. That is useful, but it also raises the bar for scoping, review, and permission design.

Limitations

Cursor inherits the failure modes of every agentic coding environment. It will happily produce clean-looking diffs that still violate architecture, skip edge cases, or misunderstand the product requirement. The richer the feature set gets, the easier it is to over-delegate and confuse velocity with correctness.

Its pricing is also more nuanced than it first appears. The subscription gets you into the workflow, but actual heavy usage depends on included model usage, on-demand usage, model routing, automations, background agents, Cursor token fees, model API fees, and whether a team also adopts review products like Bugbot. Cursor’s pricing policy treats subscription, usage, model API, Cursor token, and Bugbot usage fees as separate cost surfaces, so teams need model and budget discipline.

Practical Tips

Write repo rules before you scale usage. Cursor works much better when the editor has explicit guidance on architecture, naming, testing expectations, and non-negotiables. Keep agent tasks reviewable: ask for a plan, approve a slice, inspect the diff, then continue.

Use premium model capacity intentionally. Save it for debugging, architecture-sensitive refactors, and messy reasoning tasks. Let faster paths handle mechanical edits. If your team adopts cloud agents, mobile control, or team marketplaces, define a review protocol up front so those diffs do not become a parallel unreviewed code stream. If you enable Bugbot, keep its rules file tight and project-specific so PR comments stay useful instead of turning into generic lint cosplay.

Keep the split between interactive, ticket-driven, and event-driven use clear. Use Cursor itself for active coding and local review loops. Use Jira handoff when the ticket already contains enough acceptance criteria. Use Cursor Automations only for recurring review, monitoring, or maintenance workflows that already have a defined escalation and approval path.

Verdict

Cursor remains one of the strongest integrated coding environments on the market. It is best for developers and teams who want agents inside the IDE, connected to issue workflows, and available for recurring engineering work while still keeping human ownership of architecture, tests, and merge decisions.