Cursor alternatives revisited: what actually stuck four months after the pricing crisis

In June 2025 we wrote up the immediate migration data when Cursor’s pricing change pushed a wave of users out. The interesting question wasn’t where they went — it was where they stayed. Four months later, the Reddit data is dense and unambiguous: most heavy users didn’t pick a single replacement. They built a stack of 2-4 tools and started routing tasks between them. This piece tracks what that stack actually looks like now, who’s running it, and which of the June “obvious replacement” candidates have quietly fallen out of rotation.

The pattern: stacks, not winners

If you read the 27-upvote October 20 thread asking for Cursor alternatives, the top reply doesn’t recommend a single tool. It walks through three options simultaneously:

“Windsurf currently has chatgpt-5 codex as free, and their swe-1 model is always free. Claude 4.5 is currently 1 token for normal, 1.5 for thinking. It’s $15/mo for 500 credits. There is a free trial.”

The pattern repeats. A separate comment on the same thread describes paying $40/month for GitHub Copilot specifically because it provides 1500 Sonnet 4.5 requests per month plus 4500 Haiku 4.5 requests. Another comment recommends Kilo Code as a VS Code extension with 400+ model support, treating it as a router rather than a replacement.

But the 23-upvote “my current stack” thread from October 22 is where the actual settled-state picture comes into focus. The OP describes a full-stack developer’s year of churn — Cursor → VS Code → Claude Code → quality-degradation regret — and lands on a working solution. The top comment under that post summarizes the modal stack succinctly:

“This is my exact stack. Windsurf free, Codex $20, CC $20, GLM 4.6 $3. I use CC and GLM in Kilo, and codex in the codex extension. Sometimes I generate plans and phases with Traycer’s extension for free. Best stack I’ve had, never had limit issues.”

That’s four AI coding tools running on $43/month total subscription cost, and it represents what experienced users have actually converged on by October. The June 2025 question of “what’s the Cursor replacement” assumed a 1:1 swap. The October 2025 reality is that most people who left Cursor stopped looking for a single replacement entirely.

Where each tool earned its spot in the stack

Based on cross-referencing four months of Reddit discussion with my own daily-driver experience:

Windsurf — the “free tier that’s actually usable” anchor

Codeium’s Windsurf has emerged as a sticky anchor because of subscription economics that don’t punish casual use. Their SWE-1 model is free indefinitely (it’s not state-of-the-art but is competent for simple edits), and as of October they offer GPT-5-codex free as a promotional model. For users who need an IDE-based AI tool but don’t want to commit a $20-40 subscription to it, Windsurf is now the default fallback. The “I’ve been using Windsurf and it’s pretty much what Cursor was when Cursor was good” comment shows up repeatedly across threads — including a long endorsement under the October 20 thread about Cursor alternatives.

The honest weakness: Windsurf’s agent-loop reliability lags Cursor and Claude Code on complex multi-file refactors. It’s fine for “tab to autocomplete and ask the chat box to help me with this function,” but it’s not where heavy users are going for full agentic workflows.

VS Code + GitHub Copilot — the “I just want my IDE back” path

This was the dark horse winner of 2025. Microsoft’s bundling of Sonnet 4.5 and Haiku 4.5 into Copilot subscriptions changed the math entirely. $40/month for 1500 Sonnet 4.5 requests is roughly Cursor Pro pricing pre-crisis, but inside VS Code proper rather than a fork. A top-voted reply under the same thread captures the strategic point: “When Cursor said they had no plans to implement Copilot I knew it was because they are going to be the #1 competitor to them.” Copilot has effectively erased much of Cursor’s IDE moat over the past six months.

VS Code Insiders is the version heavy users are running for early access to Copilot features. That’s the working setup for the largest single cohort I see in Reddit discussions.

Claude Code — the “terminal-native heavy workflows” choice

Claude Code’s role in October 2025 stacks is specific: terminal-native, agent-heavy work where you want sub-agents, slash commands, and serious MCP integration. The user-experience polish is consistently called out as the best in class. The honest knock — repeated across the October 22 stack post and others — is that some users felt the model quality degraded in late August through September. Sonnet 4.5’s late-September release has mostly fixed that, but the lingering distrust is real and shows up in comments. For users on $20 Pro it’s compelling; for users on $200 Max 20x it’s a significant commitment that needs to pay off.

Codex CLI + GPT-5 — the “complement to Claude Code” choice

I wrote this comparison in depth elsewhere — the short version is that Codex CLI is the second daily driver for users who already run Claude Code, complementing rather than replacing it. The cost story on the Plus subscription is strong (heavy weekly limits but generous bursts), and GPT-5-high’s patience on large-codebase debugging is genuinely useful when Claude Code is wrong about something. Few people are running Codex CLI as their only AI coding tool, but lots of people are running it as the second.

Kilo Code / Roo Code / Cline — the “VS Code extension router” tier

These three open-source VS Code extensions form a tier on their own. They’re not differentiated by model — they’re all model-agnostic and connect to OpenAI, Anthropic, Gemini, Groq, OpenRouter, local Ollama, GLM, Qwen, and more. The differentiation is workflow patterns (architect/code/debug modes), terminal integration, and how aggressively they auto-apply changes. The October Reddit comments consistently treat them as a routing layer between cheap models and serious models, used for the kind of work where the cost-per-task matters.

A representative comment from the October 22 stack thread: “VS Code as my main IDE. Tool-wise, I stick with Kilo Code since I like the model-agnosticism they provide. For models, I use Claude Sonnet for planning, then switch to Grok Code or Haiku for coding.” This is a typical 2025-late workflow — model selection per task, mediated by an open-source router extension.

GLM 4.6 / Qwen / DeepSeek — the “cheap model for batch work” tier

The Chinese-lab models earned their place in stacks via cost. GLM 4.6 at roughly $3 per million tokens is 5-10x cheaper than frontier Western models, and is good enough for non-frontier coding tasks — generating boilerplate, simple refactors, well-specified function implementations. Most stack-building Reddit posts in October show one of these models running for the “cheap throughput” half of the work, with Sonnet or GPT-5 reserved for the cases that justify the cost. Privacy-sensitive users avoid them; everyone else uses them via Kilo Code / Cline / direct API.

What fell out of rotation

Notable in absence:

• Cursor itself. Heavy users who left over pricing in June did not come back. Cursor remained sticky for users who never tried alternatives, but the heavy cohort that left has built workflows on top of other tools. The October “looking for alternatives” posts mostly come from users still on $20 Pro who keep hitting limits.
• Cody (Sourcegraph). Once a serious contender, basically absent from October stack discussions. Stable product but no longer growing.
• Tabnine. Same pattern as Cody — still a product, no longer in the conversation.
• Bito, Continue.dev, Aider — mentioned occasionally but not as primary daily drivers in any October stack thread I read. Continue.dev specifically — once a major Cursor alternative — has dropped out of the modal stack discussions, though some users still run it for specific niches.
• Lovable, Bolt.new, v0 — the AI app-builder category lives in a different lane. People treat them as one-shot scaffolding tools, not daily coding workflows. The July “what is actually the difference between Lovable and Cursor” thread captures the framing — they’re complementary not competitive.

The multi-agent angle — a 2025 emerging pattern

One pattern worth flagging is the rise of running multiple AI agents in parallel for time-pressured projects. The 53-upvote October 22 thread “We had 2 weeks to build 5 microservices with 3 devs” describes three engineers running 5+ AI agents simultaneously, each scoped to a different microservice. The thread sparked a long debate (and significant skepticism from the comments) about whether the bottleneck was the AI or human review capacity — a top comment landed the right framing: “The bottleneck is a human to review the work. And not just glance at the diffs and checking if the concurrency looks right, but understanding the data flow and staying on top of the architecture.”

This is a real workflow that’s emerging at startups, even if it’s not yet mainstream. The tooling for it (git worktrees, sub-agents, parallel terminal multiplexing) is still rough. But the direction of travel is toward “multiple AI sessions running in parallel, human reviewing and merging” — which is a different mental model from “I sit in an IDE and ask the AI for help one task at a time.” If you want to think about where AI coding tools go in 2026, this is the signal worth tracking.

The new entrant most YouTube viewers found in October: Opencode

The most-watched alternatives video of October 2025 was DevOps Toolbox’s “Opencode Is Probably The Best Coding Agent I’ve Ever Used” (13 min, 368K views, October 17). That view count is significant — it is roughly 10x what most “Cursor vs X” videos pulled in the same month. The message that landed: there is now a serious open-source, terminal-based coding agent that supports any model, runs an internal “Zen” router that picks the latest cost-efficient model per task without taking a margin, and offers genuine pay-as-you-go economics rather than the $20 subscription model.

The author’s framing is worth quoting because it explains why so many people clicked: “I’ve been paying [Cursor] $20 for six months, probably not using 80% of it… let’s use something more comparable, like Claude Code, $17 a month, take it or leave it. With Zen, I only pay for what I use.” That is the exact frustration the June pricing crisis surfaced — the gap between what you pay and what you actually use — and Opencode is the first serious tool to address it with usage-based billing instead of a flat subscription.

Whether Opencode actually displaces Claude Code or Codex CLI for working engineers is a separate question. The video walks through Opencode’s /init (which reads existing CURSOR.md, AGENTS.md, and Copilot instructions to bootstrap), its plan/build agent modes, custom agent definitions with per-task model and temperature settings, and parallel multi-agent dispatch with session sharing across teams. Feature-wise it is broadly at parity with Claude Code’s terminal interface, and the open-source posture gives it a moat against future pricing changes that the subscription-based competitors do not have.

The honest read on Opencode in late October: it is a credible third option in the terminal-agent slot, the pay-as-you-go pricing is genuinely differentiated, and a meaningful chunk of cost-conscious users will end up trying it. Whether it sticks the way Claude Code stuck is a question for the December retrospective.

What the YouTube reviewers are still getting wrong

The format wars continue. Most YouTube AI-coding reviews in October 2025 are still framed as “which tool is best” — aiwithbrandon’s “Best AI Coding Tool in 2025? (Cursor vs Claude Code)” (39 min, 30K views, October 24) and AI LABS’ “Cursor AI Just Got a Massive Upgrade Over Claude Code” (12 min, 39K views, October 22) are representative. The Reddit reality is “which combination of tools, weighted by your specific workload and budget.” The YouTube format pushes for an answer; the Reddit format admits the answer is a stack. This gap matters because new users coming through YouTube reviews will think they need to pick one tool and stick with it, then get frustrated when limits or quality issues hit. The Reddit answer — build a stack, route by task — is more accurate and harder to communicate in a 10-minute video.

The exception worth naming is the DevOps Toolbox Opencode video above, which lands closer to the Reddit posture: here is a tool, here is what it does well, here is the workflow, here is how it fits next to your existing tools — rather than declaring a winner.

The working stack for October 2025

If you’re starting from scratch and want a sane default, here’s the stack I’d build today, with rough monthly cost:

• VS Code + GitHub Copilot ($40/mo) — primary IDE and most-used model access for in-editor work
• Claude Code on $20 Pro ($20/mo) — terminal-native heavy work, MCP ecosystem, slash commands
• Codex CLI on free ChatGPT Plus ($20/mo) — second daily driver for the workloads where GPT-5 wins
• Kilo Code extension (free, BYO API key) — routing layer for cheap model access via GLM, Qwen, DeepSeek
• API budget for GLM 4.6 or DeepSeek (~$5-10/mo) — for batch work and well-specified tasks where you want cheap throughput

Total: roughly $80-90/month for a stack that covers IDE work, terminal work, dual-model agent loops, and cost-optimized batch work. That’s roughly 4x what Cursor Pro cost in 2024, but it covers a much wider workflow surface than Cursor ever did and avoids the “I hit my limit and now I’m stuck” failure mode that drove the original June migration.

Four months on, the lesson isn’t that Cursor failed. It’s that the AI coding tools market grew up. There is no single best tool because there is no single best task — and the engineers who figured this out first are now four months ahead of the engineers still looking for the One True Cursor Replacement.