Amp is making a sharp break with the editor-sidebar era of AI coding. In a new note on its direction, the team’s argument is that the “coding agent” as most developers have come to understand it—a bundle of prompts plus a handful of IDE-integrated tools—is no longer where the interesting limitations are. With newer, highly capable coding models (the post points to the newest models), Amp says the agent wrapper itself has stopped being the bottleneck.
From agent design to workflow design
Amp’s framing is that tooling minimalism is now viable: a basic execution surface like bash is often sufficient, and finer differences—such as how diagnostics are surfaced—matter less compared to what new model generations can do “through sheer brute force.” In other words, the model can behave like a coding agent without extensive hand-holding; it’s increasingly trained to do so by default.
That shift changes where teams should spend attention. Amp’s view is that the real constraints have moved “up the stack”:
- How a codebase is organized for agentic work
- How an organization adopts and operationalizes these models
- The workflows around running, iterating, and integrating changes—not the sidebar UI
Retiring the VS Code and Cursor extensions
To align with that thesis, Amp is retiring its editor extensions for VS Code and Cursor, explicitly positioning this as “unshackling” models from the editor. The reasoning is that keeping these systems confined to an editor sidebar implicitly limits them to an assistant role—when Amp believes the models are ready to act more autonomously, including writing code and running tasks without the developer sitting in front of an IDE.
Amp sets a clear cutoff:
The Amp editor extensions will self-destruct on March 5 at 8pm Pacific Time.
The CLI as the bridge (for now)
Amp isn’t removing everything. The company says it’s keeping the Amp CLI as the primary interface “for now,” describing it as a flexible, lightweight rung on the ladder toward whatever comes next. The CLI, as presented here, is attractive precisely because it can run anywhere, change quickly, and better supports a model-centric workflow that isn’t anchored to a specific editor integration.
The throughline is consistent with Amp’s earlier messaging—“everything is changing,” as it previously put it on its April 2025 landing page. Now that the frontier has moved again, Amp is choosing to move with it, even if that means deliberately dismantling a product surface that many teams have gotten used to.