cursor.com

What I learned

Cursor got folded into Elon's empire and the fanbase is in open revolt

The r/cursor "Cursor is now part of the X subscription" thread hit 28 upvotes and 47 comments, with top commenter u/Machine2024 (29 upvotes) saying "I am a huge cursor fan... but this news is bad like really really bad... this is the point of cursor going DOWN hill... dissolving into the elon fake stokes useless group of over priced companies." The gripe is concrete: users on the $20 plan report being pushed toward $30+ for a "degraded experience and a useless twitter subscription," and third-party model allowances are gone. Cursor's own blog confirms the SpaceX acquisition closed Aug 14, 2026. The announcement itself traces back to Cursor on X, which framed it plainly: "Current Cursor subscribers can keep their plan or switch to The X Subscription. Paid plans share one usage pool across Cursor, Grok Build, and other Grok products, with twice the coding usage on Grok models as the equivalent Cursor plan," with Premium, Super, and Ultra tiers also bundling in Grok Bot. The companion announcement on x.ai, dated Oct 12, 2026, confirms the full scope: "Grok, Grok Bot, Cursor, and X Premium, all on one plan," rolling out globally "over the next few days." Cursor's own help docs spell out the mechanics, a shared weekly included pool between Grok and Cursor, with switching framed as "optional" and existing plans grandfathered in, while the pricing page confirms the weekly pool now covers "Grok 4.7, Grok 4.6, Grok 4.5, and Composer 2.5" shared across both products, up to $2,000/yr for Ultra. The official Cursor forum thread on the announcement has already run to 281 replies, with staff clarifying that "if you combine your accounts or move to The X Subscription, your Heavy plan becomes Ultra," and that third-party usage "is billed separately at API list prices, through top-ups," a detail that lines up exactly with the Reddit complaints about lost model allowances.

"Cursor is unusable anymore" became a migration manifesto

That r/cursor thread pulled 88 upvotes and 54 comments, with u/TimSylvester_ (8 upvotes) laying out a full defection: "I switched to Devin/Windsurf + Claude Code... From $60/mo Cursor to $40/mo CC + Devin." The "Whats alternative to Cursor now?" thread (76 upvotes, 170 comments) shows the same stampede - u/altervoid (37 upvotes) going "back to GitHub Copilot in VS Code," u/Loud-Custard6419 (29 upvotes) "Jumped to Zed + Claude... better than dealing with Grok." A separate r/cursor "Final thoughts on Cursor" post (80 upvotes, 52 comments) adds another defector describing swapping Cursor Ultra for "Claude 20x," with one reply noting they also jumped ship "this week."

Cursor 3 launched with Composer 2 and an agent-first pitch

The first-party Introducing Cursor 3 video from Cursor frames it as "a home for your agents," built on Composer 2, "a frontier model with incredibly high limits and very quick speeds." That framing matches Cursor's own blog post from Mar 19, 2026, which pitches Composer 2 as "frontier-level at coding and priced at $0.50/M input and $2.50/M output tokens, making it a new, optimal combination of intelligence and cost." A follow-up technical report backs the performance claim with numbers: "On CursorBench, Composer 2 scores 61.3, a 37% improvement over Composer 1.5," plus 73.7 on SWE-bench Multilingual, figures also detailed in the full Composer 2 technical report PDF, which describes it as "a specialized model designed for agentic software engineering." Tech With Tim's full Cursor 3.0 course notes the shift: "in about April of this year... they switched to an agent first interface," now running on Grok and Composer with Fable and GPT 5.6 as frontier options. Fireship's Cursor 2.0 review pegged the company at "$9.9 billion... by simply forking Microsoft's VS Code," and the comparison to the editor it forked keeps resurfacing, a Pinterest breakdown pits "Visual Studio Code" directly against Cursor on features, customization, and developer experience, while Tech With Tim's beginner tutorial reassures switchers that "if you already use VS Code, switching to Cursor takes about 2 minutes and all your extensions, themes, and key bindings come with you."

CEO Michael Truell is doing live damage control on X

@mntruell posted "Instant login and checkout with @Bot" (1,994 likes, 440K views), then spent the week firefighting - replying "@beffjezos Not intended. Messaging you to see what's going on here" (305 likes) and "@melvindvivas Fix out soon" (230 likes). Meanwhile the billing complaints kept coming: one r/cursor poster reported Cursor clawing back over-limit charges "a year later" (8 upvotes, 11 comments). Cursor's own docs confirm exactly why: "Third-party models aren't included; on Premium and above you can use them at API list price," which is the mechanism behind both the surprise invoices and the forum's clarification that combining accounts reroutes billing through the new shared pool.

The practitioner verdict is "best IDE, worst strategy."

@StevenR41985 argues "Cursor is still the best IDE-native experience. Tab completion, inline edits, refactor-in-place... fast and frictionless," while @Surendar__05 slots it cleanly: "Pick Claude for complex coding, Codex for agentic tasks, Cursor for the IDE experience." But @Ipenywis (3 likes) captures the frustration: "Cursor started focusing on their chat-only interface and forgot about improving the IDE we all enjoyed once." A Pinterest roundup of "10 Cursor AI tips and tricks every developer should know" doubles as a kind of Code Intermediate Cheat Sheet for the IDE's deeper functions, naming Fix Mode, Custom Search, Proactive Actions, Brush, Global Instructions, Multi-file Edits, Chat to Code, and Smart Completions as the features power users actually lean on once they're past the beginner stage.

Cursor shipped visual answers and Cloud Agent canvases

entrelligence's post, titled something like Cursor Brings Visual Answers Into Chat, flagged the Oct 3 feature (349 views, 19 likes): the /visualize command now renders charts and diagrams inline in the Agents Window, moving through "data, molecules and mathematics." Cursor's changelog backs this up with Oct 16 Cloud Agent canvases, and GitHub shows the plumbing - rmems wiring up .cursor/environment.json for Cloud Agents (CPU only, no GPU), alongside a parallel GitHub thread from opengovsg touching the same Cloud Agent environment config pattern, and a Custom Cursor theming tweak surfacing in the same PR history as developers personalize their agent workspaces.

The Claude Code rivalry is spilling into TikTok workflow hacks, not just pricing debates

boss_automations posted a tip titled "Stop Claude Code forgetting your work on long sessions," pointing to a plugin called "You Should Know" (/plugin enable cc-plugin-you-should-know) plus an auto-handoff script, both aimed at memory persistence during long agent sessions, the kind of workflow fix Cursor defectors are now hunting for on the Anthropic side. Meanwhile brenthaskins frames the broader shift as "vibe coding is changing fast," noting Cursor's move toward AI agents "instead of traditional code editors" splits users between those who love it and those craving more control, and one lighter TikTok aside even riffed on a Pusheen Unicorn sticker pack as the kind of throwaway distraction developers screenshot mid-debugging-session while their seven AI agents go rogue.

The practitioner verdict is "best IDE, worst strategy," continued

A Pinterest infographic comparing "Cursor vs Claude Code" breaks the choice down to "Workflow: Driving vs. Briefing" and "Model Access: Any Model vs. Anthropic Only," the same model-access tradeoff driving the Reddit churn above.