Cursor Compile 26: From IDE to Agent Platform (Category AI4SDLC)
I watched the opening keynote from the first Cursor Compile 26 conference, published on 22 June 2026. It is a good product announcement because it openly signals a change of category: Cursor wants to become an agent platform for development, beyond being an AI IDE.
Several speakers took part: Cursor co-founder and CEO Michael Truell, Kevin Niparko and Tomas Reimers. Truell says Cursor has become agent-first in recent months. According to the company, more than 95% of users primarily use Cursor as an agent, and agent requests outnumber requests to assistance features such as Tab by roughly 5 times. These are vendor claims, of course; what matters here is the trend more than the precise figures. A series of announcements follows.
1️⃣ Cloud agents (documentation) Cursor describes a dedicated working environment for the agent, beyond simply running it on a server. It has its own computer: a repository clone, dependencies, access to build systems and internal toolchains, and the ability to run tests, produce demos and screenshots, and continue iterating. This is exactly the layer called a harness in Google’s whitepaper “The New SDLC: From Vibe Coding to Agentic Engineering”; see my discussion. A model alone does not bring a task to a production-ready result: it needs a harness, an environment and verification. The speakers say their cloud agents have become 3 times faster, reached three nines of reliability and completed more than 6 million runs. Their example was Amplitude’s migration of 20 000 React components to Tailwind through automations and a custom migration agent.
2️⃣ Cursor Mobile At first glance, this is a mobile app. The more interesting engineering point is that Cursor is designing for a developer’s day in which agents keep working while the person is away from their laptop. A phone lets you see running and blocked agents, inspect artifacts, annotate screenshots and prompt an agent to continue. This fits my earlier discussion of Zack Proser’s point about human attention becoming the bottleneck. As agents work longer and more autonomously, the main interface shifts toward unblocking them in time and checking results.
3️⃣ Origin, a strategic announcement of an agent-native Git platform Tomas Reimers, Graphite’s co-founder, presented it. He joined Cursor after its acquisition of Graphite in January. The logic is straightforward: if agents generate more lines of code, commits and pull requests, Git infrastructure, review and CI become the next bottlenecks. Origin promises a platform where people and agents create repositories, manage changes and work through APIs, MCP and third-party apps, with the platform helping resolve merge conflicts, CI failures and review comments.
This gives me strong déjà vu from my posts on GitLab Act 2 and the AIDev PR dataset. GitLab discussed machine-scale Git and lifecycle orchestration; AIDev proposed examining the whole path from issue to PR, review, CI and merge. Cursor is approaching the same problem from the IDE: if the agent becomes the main producer of changes, the platform needs to see and retain the complete history of each change.
4️⃣ A new Cursor foundation model Truell said it is large, trained from scratch rather than starting from an open-source base, uses 10-20 times more compute than previous Cursor models and should arrive “in the coming weeks.” Cursor describes it as a model for the broader role of an engineering colleague, not simply coding: tools, long-range planning, testing, interacting with interfaces and a clear user experience showing what the agent changed. The competition now spans the model, product and agent environment, beyond better autocomplete.
Cursor is moving in the direction I’ve repeatedly described as Software Engineering 2.0, most recently yesterday in my talk at Highload++ in St. Petersburg. Together, these announced capabilities form a new system for developing production software.
#AI #AI4SDLC #Engineering #Agents #DevTools #PlatformEngineering #Management #DevEx