Cursor 2.0 vs smolvm

“The primitive here is a goal-directed code agent with a planning layer — not just autocomplete or single-file edits, but something that can read a codebase, form a plan, and execute changes across multiple files with rollback context. The DX bet is that async background tasks let you kick off a large refactor and come back to a diff for review, which is exactly the right place to put the complexity — at review time, not setup time. The moment of truth is whether the agent's plan step is legible: if it can show you what it intends before it touches 40 files, that's a tool that survived first contact. The specific decision that earns the ship is the separation between planning and execution — that's not a wrapper, that's a thought-out architecture.”

“This is the missing layer for anyone running AI agents that execute code. Docker containers have always been too porous for untrusted execution, and smolvm's sub-200ms coldstart means you can spin a fresh VM per agent turn without killing your latency budget. The AGENTS.md is a thoughtful touch — shows the authors actually understand the workflow.”

“Direct competitors are GitHub Copilot Workspace and Aider — both doing multi-file agent edits — so Cursor 2.0 is not first here, but it's the most polished IDE-native implementation by a measurable margin. The scenario where this breaks is any refactor that requires semantic understanding of runtime behavior: rename a method that's called via reflection, reorganize a microservice boundary, or touch anything with a non-trivial test suite that the agent can't run. Background tasks specifically collapse when the repo state changes under the agent mid-run — a problem nobody has solved cleanly. What kills this in 12 months is not a competitor but Microsoft: if VS Code ships a first-party agent mode with the same model access and GitHub integration, Cursor's distribution advantage shrinks fast. What keeps it alive is that Cursor's team has shipped faster and with more taste than any IDE team in memory, and that execution track record is the real moat.”

“At v0.5.18 this is still early software and the docs are sparse. libkrun has its own surface area of bugs, and running microVMs at agent-loop speed on macOS introduces a whole class of Apple Hypervisor Framework edge cases. I'd wait for v1.0 and a production case study before betting real workloads on this.”

“The thesis Cursor 2.0 is betting on: within 2-3 years, the primary unit of developer work shifts from writing code to reviewing and directing code — and the IDE becomes an orchestration surface, not a text editor. That's a falsifiable claim, and background task scheduling is the earliest production artifact of that world. What has to go right is model reliability on multi-step planning reaching the threshold where false positives in diffs don't cost more time to review than the task saved — we're close but not there on large repos. The second-order effect that nobody is talking about: if background agents normalize, code review culture transforms. Reviewers stop reviewing author intent and start reviewing agent output, which requires different skills and different tooling entirely. Cursor is riding the trend line of model capability outpacing IDE UX — they're on-time, not early, but executing better than anyone else on the same trend.”

“Every autonomous agent that executes code needs a proper sandbox — not a polite request for the agent to be careful. smolvm represents the infrastructure layer that makes truly autonomous code execution safe enough to deploy at scale. This kind of primitive is foundational for the agentic software era.”

“The job-to-be-done is clear and singular: execute a complex, multi-file code change that would take a developer 30-120 minutes, reduce it to a review task. Background tasks extend that JTBD to long-running work without occupying the developer's attention — that's a coherent expansion, not feature sprawl. The completeness question is real though: if the agent can't run tests and interpret failures in the same loop, users still need to dual-wield with a terminal and a test runner, which means the job is only half-done. The specific product decision that earns the ship is the async review model — treating the agent's output as a PR-like artifact rather than live inline edits is the right opinion about how senior developers actually want to interact with autonomous changes.”

“For anyone building AI tools that touch code, smolvm means you can let your AI actually run things without fear. That unlocks a whole category of 'show me the output' UX patterns that weren't safe before. Less time explaining sandboxing to users, more time shipping features.”