A developer recently shared their journey through every AI-powered editor on the market. Cursor, Windsurf, VSCode with Claude extensions, Warp, cmux. Each one promised to be the last stop. None of them were. They ended up on Ghostty with Neovim and Claude Code running as a sidebar. Zsh, Starship, fzf, ripgrep, bat. No IDE. No electron wrapper. Just the shell.
This isn't one person's quirky preference. It's a pattern.
What This Means
The AI editor boom was never about the editors themselves. It was about reducing friction between developers and AI capabilities. For people new to coding, the GUIs worked. But for developers who already lived in terminals, adding a graphical layer on top of AI pair programming introduced new friction without removing the old.
When you code in an IDE, you split attention between the editor, the AI assistant panel, and your terminal. When you code in a terminal with Claude Code or Codex CLI, the AI becomes a first-class citizen of the shell. The interface disappears. You're left with prompt, code, iterate.
The cycling between editors costs real time. Every switch means re-learning keybindings, migrating configs, adjusting muscle memory. The terminal doesn't have this problem. It's been the same paradigm for fifty years. When an AI tool runs in that environment, it inherits that stability.
There's also something behavioral going on. Power users resist tools that dictate workflow. An IDE that owns your project structure, sidebar, and file tree feels prescriptive. A terminal feels like a raw instrument you shape yourself.
The Bigger Picture
The developer tooling market is splitting into two distinct experiences, and that's probably healthy.
AI-native IDEs serve a real audience. They reduce the intimidation of staring at a blank editor, surface capabilities gradually, and package everything in a familiar GUI. Cursor knows this, which is why they just shipped Cursor 3 with an agent-first architecture that puts orchestration front and center. They're not ignoring the terminal trend. They're trying to absorb it.
But the numbers tell a different story about where the cutting edge lives. Claude Code hit a 72.5% resolution rate on SWE-bench Verified. Independent tests with Cursor using Claude Sonnet as its backend land in the 55-62% range. Same underlying model, different interface, measurably different outcomes. The terminal isn't just a preference. It's a performance advantage.
What's interesting is that plenty of developers aren't choosing sides at all. Reports from early 2026 show devs spending $40/month running both tools, using Cursor for visual code review and Claude Code in the integrated terminal for the heavy lifting. Migrations, E2E tests, multi-file refactors. The IDE becomes a viewer. The terminal does the work.
This means the competitive landscape isn't heading toward a single winner. It's converging. Cursor 3's agent mode borrows heavily from the terminal-first philosophy. Claude Code now runs inside VS Code. The tools are absorbing each other's strengths, and the boundary between "IDE" and "terminal" is blurring.
What Happens Next
The convergence will accelerate. Expect every IDE vendor to ship deeper terminal integration within the year, and expect terminal tools to gain lightweight UI overlays for code review and diffing. The pure-terminal and pure-IDE camps will shrink as hybrid workflows become the default.
The more interesting shift is where these tools get used. If the terminal is the most effective interface for AI-assisted coding, it doesn't need to live on a desktop. It runs on a server. You SSH in. The machine doing the computation doesn't need to be the machine in front of you, and the device in front of you doesn't need to be a laptop.
Final Thoughts
The editor carousel is a symptom, not the disease. Developers keep switching because the GUI isn't where the leverage is. The leverage is in the model, and the most direct path to the model is the terminal. Once you internalize that, the carousel stops. Tools like Onepilot already let you run these terminal workflows from your phone, which makes the whole question of "which desktop editor" feel increasingly beside the point.