Cursor 3 Released: The IDE Becomes Irrelevant, Agent Console Takes Over, The VS Code Era Begins to Fade

marsbitPublicado a 2026-04-08Actualizado a 2026-04-08

Resumen

Cursor 3, codenamed Glass, represents a fundamental shift in AI-assisted development by replacing the traditional code editor with an agent management console as the primary interface. While engineers can still write code, the core design philosophy now centers on users spending most of their time directing AI agents, reviewing their outputs, and deciding which tasks to deploy. Key features include multi-repository support, a unified sidebar for all agents (local and cloud), and Cloud Handoff, which allows seamless movement of agent sessions between local and cloud environments. This release is part of Cursor's accelerated response to competitive pressure from tools like Anthropic's Claude Code. The company also recently launched Automations for triggering agents automatically, Composer 2 (its proprietary model claiming superior performance to Claude Opus), and self-hosted cloud agents for enterprise customers. The transition signals a broader industry paradigm shift where agent orchestration becomes the new control plane, similar to how cloud consoles replaced SSH for infrastructure management. This challenges the decades-long dominance of IDEs like VS Code, suggesting that software engineering roles are evolving toward overseeing AI agents rather than directly editing code. The architectural debate now centers on whether this orchestration layer should exist inside the IDE (Cursor, Google), as a separate tool (Anthropic, OpenAI), or be omnipresent.

Cursor 3 replaces the traditional code editor with an agent management console, marking a significant shift in both AI-assisted development tools and developer workflows.

As the fastest-growing AI code editor in terms of revenue, Cursor has released its first non-code editor product.

Cursor 3 (codenamed Glass) is built from the ground up, featuring an agent management console as the main interface, relegating the traditional IDE to a secondary position for the first time. Engineers can still write code in it, but the core design philosophy of this product has shifted to "users will spend most of their time scheduling agents, reviewing outputs, and deciding which tasks to release." The space where the file tree was once displayed has now been replaced by a prompt input box.

For months, the status of coding tools has been increasingly overshadowed by AI models. The emergence of Cursor 3 is a direct result of this $2 billion annual revenue company accepting this reality and betting its entire product line on it. This shift mirrors the experiences of infrastructure engineers in the past.

Cloud control panels replaced SSH terminals. Kubernetes controllers replaced manual server configuration. Today, the orchestration layer is replacing the code editor as the primary interface. Although the trend is the same, the stakes of this wave of change are higher because the abstraction layer being downgraded is the underlying architecture that developers have used for 40 years.

What Cursor 3 Brings

Cursor was born in 2022 as a fork of VS Code and has now evolved into a sibling version built entirely around agents. Cursor states that the new interface is "built from the ground up, agent-centric," and treats the traditional IDE as an alternative that can be switched to at any time.

The workspace natively supports multiple repositories, allowing agents and users to operate simultaneously across different repositories, while all local and cloud agents are displayed in a unified sidebar. This sidebar pulls agents from all of Cursor's interfaces, including sessions launched from mobile devices, web clients, Slack, GitHub, and even Linear. Cloud agents generate demos and work screenshots, allowing engineers to quickly understand changes without pulling the code locally.

The most prominent feature in the new version is Cloud Handoff. Users can move running agent sessions from their laptop to the Cursor cloud, ensuring they continue to run when the computer is shut down, and pull them back locally for editing and testing on the desktop when ready, and vice versa. Users can start tasks in the cloud and pull them back when they need to take control. This ability to port sessions between local and cloud environments has been a major weakness of most competing products.

One can view the emergence of Cursor 3 as a significant shift from managing a single server to managing a cluster of servers through a control plane. While users can still SSH into a server when necessary, the control plane has become the hub for decision-making, workload allocation, and viewing system status. Cursor 3's approach to agents represents a similar major shift, where the IDE is analogous to SSH, and Glass is analogous to the control plane.

Transformation Driven by Pressure

The release of Cursor 3 is no accident. Over the past six weeks, Cursor has launched what I call an "accelerated product offensive." In late March, Fortune published a feature describing Cursor's situation as a classic case of the "innovator's dilemma," which quickly sparked strong reactions. Prior to this, Bloomberg had just pointed out that Cursor's annualized revenue officially surpassed $2 billion in February 2026, doubling in just three months.

However, Fortune found that Anthropic's terminal-first programming agent, Claude Code, had grown its annualized revenue to $2.5 billion in just over a year, winning favor with over 300,000 enterprise customers. Developers publicly expressed their intention to abandon Cursor and switch to Claude Code. A Cursor investor told Fortune that several startups in his portfolio were considering terminating their contracts with Cursor. In March, reports indicated that although Cursor was seeking a new round of funding with a valuation of approximately $50 billion, market confidence in its future development was crumbling.

In response, Cursor quickly took three major steps to address these challenges. On March 5, the company released the Automations system, which triggers agents based on GitHub events, Slack messages, and timers without human intervention.

On March 19, Cursor released Composer 2, its first self-developed model based on MoonDarkSide's open-source Kimi K2.5.

Cursor claims that Composer 2 scored 61.3 on its proprietary CursorBench test, higher than Claude Opus 4.6's 58.2, with lower cost per unit token. It is important to note that CursorBench is Cursor's own evaluation suite.

Also in March, Cursor enabled self-hosted cloud agents, allowing Fortune 500 companies to run Cursor agents on their internal infrastructure.

Then came the official release of Cursor 3. Three products in one month, with a complete interface overhaul. This pace is clear evidence of the company's conviction that its business domain is being redefined.

Structural Shift

The significance of Cursor's transformation lies in its suggestion of a paradigm shift far beyond a single company. All major players in the AI-assisted development space have now reached a consensus that agents need their own dedicated orchestration interface. The disagreement among vendors lies in where this interface should reside, creating interesting differences in developer tool architecture.

Anthropic's Claude Code adopts a terminal-first model, completely abandoning the Integrated Development Environment (IDE). The command-line interface (CLI) is the orchestration layer, where developers work via natural language commands in the shell. Anthropic later added a browser-based interface and a desktop application at claude.ai/code, but still considers the terminal the core, meaning the orchestration layer is completely separate from the editor.

OpenAI has chosen a different path. Codex now encompasses a standalone desktop application, a command-line interface, IDE extensions for VS Code and its forks, plus a cloud interface at chatgpt.com/codex. Among these, the desktop application becomes the "command center" for managing parallel agents, viewing diffs, and running work across projects. OpenAI's philosophy is that the orchestration layer should be ubiquitous, accessible from any interface developers use.

"For the past four decades, the software development paradigm has been defined by the code editor. Cursor 3 bets everything on the belief that supervising agents will become more important than editing files."

Google's approach is closest to Cursor's. After paying Windsurf a $2.4 billion licensing fee and bringing its CEO and core engineers into DeepMind, Google launched Antigravity—an agent-centric IDE offering two distinct modes. The editor view contains the traditional programming environment, while the manager interface allows developers to generate, orchestrate, and observe multiple agents in parallel within the workspace. Agent orchestration and code editing coexist within the same application but are presented in different views.

Cursor 3 also adopts this internal IDE model but takes it a step further. Glass sets the agent console as the default view, with the editor becoming an alternative view. Google's Antigravity considers both views equally important, reflecting a difference in emphasis. In other words, the two companies have different judgments about where developers will ultimately spend their time.

We can draw an analogy to the evolution of cloud infrastructure. When AWS introduced its management console, users did not stop using SSH. But SSH was no longer the place for making infrastructure decisions; the console became the control plane, and SSH became an occasional debugging tool.

Anthropic and OpenAI believe the orchestration layer can operate as a standalone application, separate from the IDE. Cursor and Google believe the orchestration layer needs to coexist with the editor so developers can directly view the code when agents make mistakes. The industry generally agrees that agent orchestration will become the new main interface, but consensus on the specific architectural design has not been reached.

What This Means for Developers

Currently, the practical impact of this change is mainly reflected in the following three aspects:

1. Model Selection Becomes Infrastructure

Cursor sets Composer 2 as the default model but still allows developers to switch to Claude, GPT-5.4, and Gemini based on the conversation. The model driving the agents is now an infrastructure-level decision, similar to choosing a database or cloud region, and token economics will form as scale increases.

Cursor's published pricing for Composer 2 Standard is $0.50 per million input tokens and $2.50 per million output tokens (prices as of March 2026), significantly lower than the pricing of frontier models from Anthropic and OpenAI.

For teams running dozens of parallel agents, such pricing is undoubtedly more attractive than feature sets or UI preferences.

2. VS Code's Moat is Drying Up

Cursor forked from VS Code, inheriting its extension ecosystem and enabling instant distribution. Cursor 3, however, charts a new course, aiming to create differentiated advantages. If agent-centric interface design ultimately wins, the importance of VS Code extensions will decline significantly. Microsoft clearly needs to keep a close eye on this trend.

The assumption of VS Code as the center of the developer tool universe has held for nearly a decade but is now gradually unraveling.

JetBrains faces similar pressure. As the primary interaction shifts from editing files to managing agents, the competitive advantages of traditional IDEs in programming intelligence and refactoring tools will also evaporate.

3. Workflows Change First, Development Roles Transform Later

Cursor 3 posits that engineers will spend significant time reviewing diffs generated by agents, validating screenshots generated by cloud agents, deciding which tasks to push to the cloud and which to keep local, and managing PR workflows.

This is fundamentally different from previous code writing methods and skill requirements, meaning programming is shifting more towards engineering manager or platform operations roles rather than traditional software developers. In other words, the role of the software engineer is merging with that of an application-layer systems operator.

"The role of the software engineer is merging with that of an application-layer systems operator."

Cursor's own development trajectory reflects this shift. The company acquired the code review platform Graphite in December 2025. As CEO Michael Truell stated, as AI accelerates code generation, code review is becoming the new bottleneck.

Cursor 3 extends this logic further: agents write the code, Graphite reviews it, and the engineer's job is to coordinate the two. The importance of the Integrated Development Environment (IDE) takes a back seat.

Future Outlook

The orchestration layer for AI programming agents is now a new product category. All major manufacturers have launched related products. The unresolved question is at the architectural level. Should the orchestration layer exist within the IDE, outside it, or simultaneously across all interfaces?

Anthropic and OpenAI are betting on standalone tools. Cursor and Google are betting on integrated consoles that include an IDE. Whose choice aligns more closely with the real trend will win the support of developers in the next decade, just as the cloud control plane debate in the early 2010s determined today's infrastructure giants.

For the past forty years, the way software is built has been defined by the code editor. Cursor 3 bets on the idea that supervising agents is more important than editing files. Cursor is not killing the IDE; it is demoting it.

If this assessment is accurate, what we are seeing might be the last code editor in human memory. The future remains to be seen.

Original Article Link

https://thenewstack.io/cursor-3-demotes-ide/

This article is from the WeChat public account "AI前线" (AI Frontline), author: Janakiram MSV, translator: Nuclear Cola

Preguntas relacionadas

QWhat is the main change introduced in Cursor 3 compared to traditional IDEs?

ACursor 3 replaces the traditional code editor with an agent management console as the primary interface, shifting the core design to focus on scheduling agents, reviewing outputs, and deciding which tasks to deploy, while the IDE becomes a fallback option.

QHow does Cursor 3's Cloud Handoff feature work?

ACloud Handoff allows users to move a running agent session from their laptop to the Cursor cloud, ensuring it continues running even when the computer is off. Users can later pull it back to the local desktop for editing and testing, or vice versa, enabling seamless transitions between local and cloud environments.

QWhat competitive pressure led to Cursor's rapid product releases, including Cursor 3?

ACursor faced pressure from Anthropic's Claude Code, which reached $2.5 billion in annualized revenue and attracted over 300,000 enterprise customers, leading some developers to switch. This prompted Cursor to launch three major products in a month, including Automations, Composer 2, and Cursor 3, to stay competitive.

QHow do different companies like Anthropic, OpenAI, and Google approach the agent orchestration layer in developer tools?

AAnthropic uses a terminal-first approach with a separate CLI and browser-based interface for orchestration. OpenAI offers a ubiquitous orchestration layer across desktop apps, CLI, IDE extensions, and cloud interfaces. Google and Cursor integrate the orchestration layer within the IDE, with Cursor 3 making the agent console the default view and Google's Antigravity offering equal emphasis on both editor and manager views.

QWhat does Cursor 3 suggest about the future role of software engineers?

ACursor 3 indicates that software engineers will spend more time reviewing agent-generated outputs, managing PR workflows, and coordinating tasks between local and cloud environments, shifting their role towards that of an application-level system operator rather than a traditional code writer.

Lecturas Relacionadas

"Water Scarcity": The Hidden Fatal Flaw of AI Infrastructure

“Water Scarcity: The Hidden Vulnerability of AI Infrastructure” In June 2026, SpaceX revised its IPO prospectus to highlight a core resource constraint alongside power and processors: water. This move signals a pivotal shift where water scarcity has transformed from an operational cost to a major, uncontrollable investment risk, directly threatening AI data center expansion. The scale of the problem is immense. U.S. data centers consumed an estimated 17 billion gallons of water for direct cooling in 2023, with indirect water use for power generation exceeding 211 billion gallons. Giants like Google alone use billions of gallons annually, with single sites consuming volumes equivalent to a medium-sized city. This water is largely “consumptive,” evaporated into the atmosphere and lost. This massive demand is colliding with scarcity. Tech companies are building “water tigers” in arid regions, sparking community protests in places like Mexico and Arizona, where data centers can legally use millions of gallons daily—enough for tens of thousands of residents. These conflicts are not about illegality, but about a mismatch between historic water allocation frameworks and new, colossal demand. The consequences are real. Community opposition, largely centered on water, has reportedly stalled or canceled $64 billion in U.S. data center projects over two years. Simultaneously, investors are pressuring companies for greater water footprint transparency, viewing it as a financial risk, not just an ESG metric. Technological solutions like air or liquid cooling involve trade-offs between water and electricity use, with final choices dictated by local constraints. The irony is stark: while industry leaders envision AI as a utility “like water,” its physical infrastructure is straining real-world water supplies. The race for AI supremacy may ultimately be governed not by the fastest chip, but by the slowest water meter.

marsbitHace 37 min(s)

"Water Scarcity": The Hidden Fatal Flaw of AI Infrastructure

marsbitHace 37 min(s)

Global Card Issuance Enters a Compliance-Driven Era: WasabiCard is Building the Next-Generation Payment Infrastructure

Global card issuance is entering a compliance-driven era, with WasabiCard building next-generation payment infrastructure. The platform asserts that as stablecoins increasingly enter cross-border payments, corporate settlements, and global commerce, the industry is shifting focus from "availability" and "growth-driven" models to long-term, compliant operation under global frameworks. Competition will center on sustainable compliance and global infrastructure capabilities. Stablecoins are evolving from on-chain assets into key payment tools in global business, with card issuance acting as critical infrastructure connecting digital assets to traditional payment networks like Visa and Mastercard. This expansion has revealed structural issues, including cross-regional issuance, BIN resource management, and insufficient AML and risk controls. In response, the industry is moving away from reliance on "grey efficiency" towards prioritizing compliance, risk management, and long-term operational stability. WasabiCard outlines its strategy: collaborating with licensed principals and local partners for localized operations, building robust KYC/AML systems, strictly separating commercial and consumer BIN usage, and enhancing global issuance, payment, and cross-border fund flow infrastructure. The goal is to build stable, scalable payment infrastructure amid evolving global regulations, shifting industry competition from scale to infrastructure capability. As stablecoins integrate further with global commerce, payment infrastructure will become a fundamental, embedded component of internet business. WasabiCard will continue to develop capabilities in global card issuance, stablecoin payments, cross-border fund flows, and API-driven financial workflows.

marsbitHace 47 min(s)

Global Card Issuance Enters a Compliance-Driven Era: WasabiCard is Building the Next-Generation Payment Infrastructure

marsbitHace 47 min(s)

Zhou Hang: How Much Is SpaceX Really Worth?

**Zhou Hang: How Much is SpaceX Really Worth?** SpaceX, arguably one of the greatest industrial companies of the past 50 years, is reportedly targeting a staggering $1.75 trillion valuation in its potential IPO. However, the author argues this figure is inflated by approximately $1.25 trillion when assessed through standard financial metrics. The analysis begins by acknowledging SpaceX's undeniable success: drastically reducing launch costs, achieving near-monopoly in commercial launches, and building the strategic Starlink network. Its achievement surpasses even Tesla's, given it disrupted a state-monopolized industry. Despite this greatness, a $1.75 trillion valuation places SpaceX above the combined market cap of Boeing, Lockheed Martin, Northrop Grumman, RTX, and General Dynamics. Projecting optimistic 2030 revenues of $50-80 billion and applying generous tech-sector multiples yields a "reasonable" valuation range of $500 billion to $1.2 trillion. The $1.25 trillion gap is attributed to three non-financial premiums: 1. **Long-term vision premium** for future Starship-enabled markets (e.g., space-based computing). 2. **Sovereign asset/strategic premium**, as SpaceX is deeply integrated into U.S. national security. 3. **Retail narrative/Musk cult premium**, driven by a heroic story and personal following. Post-IPO, three scenarios are outlined: valuation solidifying (25% probability), sideways volatility as narrative outpaces reality (50%), or a re-rating down to $800B-$1.2T if execution falters or Musk-related risks emerge (25%). The probability-weighted expected value is $1.3-1.5 trillion, suggesting negative expected returns for those buying at the IPO price. The conclusion advises investors to separate the company's excellence from its stock price. Buying at the IPO likely prices in excessive optimism. A more prudent strategy would be to wait for key milestones (e.g., Starship V3 stability) or a significant price correction before investing, or to treat an early purchase as a long-term, high-conviction hold with limited position size, not a short-term bet.

链捕手Hace 52 min(s)

Zhou Hang: How Much Is SpaceX Really Worth?

链捕手Hace 52 min(s)

Trading

Spot
Futuros

Artículos destacados

Cómo comprar ERA

¡Bienvenido a HTX.com! Hemos hecho que comprar Caldera (ERA) sea simple y conveniente. Sigue nuestra guía paso a paso para iniciar tu viaje de criptos.Paso 1: crea tu cuenta HTXUtiliza tu correo electrónico o número de teléfono para registrarte y obtener una cuenta gratuita en HTX. Experimenta un proceso de registro sin complicaciones y desbloquea todas las funciones.Obtener mi cuentaPaso 2: ve a Comprar cripto y elige tu método de pagoTarjeta de crédito/débito: usa tu Visa o Mastercard para comprar Caldera (ERA) al instante.Saldo: utiliza fondos del saldo de tu cuenta HTX para tradear sin problemas.Terceros: hemos agregado métodos de pago populares como Google Pay y Apple Pay para mejorar la comodidad.P2P: tradear directamente con otros usuarios en HTX.Over-the-Counter (OTC): ofrecemos servicios personalizados y tipos de cambio competitivos para los traders.Paso 3: guarda tu Caldera (ERA)Después de comprar tu Caldera (ERA), guárdalo en tu cuenta HTX. Alternativamente, puedes enviarlo a otro lugar mediante transferencia blockchain o utilizarlo para tradear otras criptomonedas.Paso 4: tradear Caldera (ERA)Tradear fácilmente con Caldera (ERA) en HTX's mercado spot. Simplemente accede a tu cuenta, selecciona tu par de trading, ejecuta tus trades y monitorea en tiempo real. Ofrecemos una experiencia fácil de usar tanto para principiantes como para traders experimentados.

369 Vistas totalesPublicado en 2025.07.17Actualizado en 2026.06.02

Cómo comprar ERA

Discusiones

Bienvenido a la comunidad de HTX. Aquí puedes mantenerte informado sobre los últimos desarrollos de la plataforma y acceder a análisis profesionales del mercado. A continuación se presentan las opiniones de los usuarios sobre el precio de ERA (ERA).

活动图片