Is Cursor AI Editor the Future of Coding? A Deep Dive into New Features and Risks

Last weekend Anysphere officially released version 1.0 of its AI editor Cursor, bringing a suite of new capabilities.

The major additions include:

BugBot : an AI assistant that automatically scans pull requests, comments on detected issues, and links to the relevant code in Cursor.

Background Agent : a remote‑environment agent that can clone a GitHub repository, work on a separate branch, and push changes back; it runs in the cloud and also requires Max mode.

Memories : a feature that records AI conversation context and facts for later reference, configurable in settings.

MCP one‑click installation : a curated list of officially certified tools (GitHub, Figma, Notion, Stripe, Playwright, etc.) that can be installed directly from Cursor.

You can check your current version via a terminal command; if it is not 1.0, an upgrade is recommended because the changes are substantial.

BugBot: Automatic PR Review

BugBot connects to GitHub, triggers on each PR update, posts comments on identified problems, and provides links to the corresponding code in Cursor. Using BugBot requires enabling Cursor’s Max mode, which is available to Pro subscribers (US$20/month).

Background Agent: Remote‑Running Smart Agent

Background Agent is currently in preview. It automatically clones a GitHub repo, works on an isolated branch, and pushes modifications. The remote environment may become a paid service in the future, but for now it is billed only by AI token usage. Like BugBot, it also requires Max mode.

The documentation warns that the agent expands the attack surface and has not undergone third‑party security audits. Because the agent has read‑write access to code repositories, it could be exploited via prompt‑injection attacks, where malicious web pages inject hidden commands to steal code or sensitive data.

MCP Tools and One‑Click Deployment

The MCP server now supports one‑click installation of tools inside Cursor. Anysphere maintains an official list of certified MCP tools, including GitHub, Figma, Notion, Stripe, and Playwright, and developers can add deep links to Cursor in their documentation.

Competition Landscape

Cursor is built as a fork of Visual Studio Code and was first previewed in 2023. Its rivals include VS Code + GitHub Copilot, Windsurf (formerly Codeium), Amazon Q Developer, Google Gemini, Mistral Code, Tabnine, Claude Code (Anthropic), and Aider. Many of these tools integrate as IDE plugins or run in the terminal.

According to recent data, the PR merge rate—a key metric for AI coding assistants—shows OpenAI’s Codex at 83.3% and Cursor at 77%, placing them as the top two performers.

Cursor’s Dilemma

Four main challenges emerge:

Developer habits: many prefer a “multi‑IDE + multi‑task + multi‑AI” workflow, making Cursor’s single‑IDE approach feel restrictive.

Competitive parity: rivals offer seamless integration with existing toolchains, narrowing any advantage Cursor might have.

Revenue vs. profit: despite reporting rapid growth and $300 M annualized revenue, the user base may be far smaller than the numbers suggest, raising concerns about sustainable profitability.

Security and trust: the Background Agent’s prompt‑injection risk is openly documented, highlighting unresolved safety issues.

“I think building a forked IDE on VS Code is a strategic mistake. I only consider AI tools that can integrate into my current IDE (VS Code + Rider).”

Some community members speculate that Cursor’s best path forward could be acquisition by one of the seven major AI companies, given its user base, revenue, and staff size.

Overall, if Cursor cannot overcome the limitation of being usable only within its own IDE, its growth may soon hit a ceiling, while security concerns continue to loom.