Cursor Composer 2.5 Launch

Composer 2.5 didn't get a new brain — it got a much better tutor. The model still rides on Moonshot's open-source Kimi K2.5 checkpoint, the same base Cursor used for Composer 2 ^[3]. What changed is how Cursor spent its compute on top: roughly 85% of total compute went into Cursor's own post-training and reinforcement learning, including 25x more synthetic tasks than Composer 2 ^[1][6]. The signature trick is what Cursor calls Targeted RL with Textual Feedback: instead of grading an entire multi-step coding rollout against a single end-of-episode reward, the system inserts localized hints precisely at the point where the model errs, sharpening credit assignment over rollouts that span hundreds of thousands of tokens ^[1].

Cursor also leans on a 'feature deletion' technique where the agent is forced to reimplement removed code against an existing test suite — a synthetic curriculum that pushes the model toward sustained, verifiable work rather than one-shot completions ^[1][5]. The whole stack runs through a Sharded Muon optimizer that hits a 0.2-second optimizer step time on a 1T-parameter model, which is what makes throwing 25x more synthetic curriculum at the model economically tractable in the first place ^[1][6].

Composer 2.5's headline pricing is $0.50 per million input tokens and $2.50 per million output tokens, with a faster, more expensive variant at $3/$15 ^[1]. That lands roughly an order of magnitude below Opus 4.7's published rate card for the same tier of work ^[6][7].

For Cursor, the strategic upside is COGS: every developer who flips the default from Claude to Composer 2.5 turns an external API bill into amortized post-training and inference cost on a model they own. The r/cursor community framed it as roughly a 10x cost gap alongside the double-usage promo, but the discussion underneath is less convinced — practitioners running long agentic sessions argued that when each turn re-processes tens of thousands of context tokens, the realized cost gap narrows considerably, blunting the per-token math.

Cursor and Anthropic have always had an awkward relationship: Claude has been the default coding model inside Cursor while Anthropic ships Claude Code as a direct rival. Making Composer 2.5 the default in the model picker — with Composer 2 still selectable but Claude no longer privileged — is the clearest signal yet that Cursor wants to control its own destiny ^[4].

The internal proof point Cursor highlights is that 35% of merged pull requests at the company are now created by autonomous agents, an implicit pitch that the model is good enough to run their own dogfood loop ^[6]. Hacker News commenters reading the launch framed it the same way: Cursor is hedging against a single-vendor coding stack ^[8].

Reddit's reception was sharper than the official narrative. On r/vibecoding, the launch screenshot drew accusations of benchmaxxing — commenters argued that the chart's framing buried Opus 4.7 leading on most cells, and at least one developer reported that Composer 2.5 broke their codebase before they rolled back to Opus and got the task done in a single shot.

The harshest community read — that Cursor 'just has absolutely no moat' as a VS Code fork — is exactly the critique Composer 2.5 is meant to rebut by turning the IDE into a vertically integrated model-plus-harness product. Whether that argument lands depends on how Composer 2.5 performs in the long, messy sessions that benchmarks underweight, not on the screenshots ^[8].

Buried in the technical write-up is the most interesting forward signal: Cursor's next-generation model is being co-trained with SpaceXAI on the Colossus 2 cluster using roughly 10x more total compute — million-H100-equivalent scale ^[1][7]. Combined with Cursor's Sharded Muon optimizer hitting a 0.2-second optimizer step time on a 1T-parameter model, the operational picture is that Composer 2.5 is a proof point on a borrowed base, and the real bet is a much larger Cursor-native model still in training ^[1][6].

If that ships within Cursor's typical cadence, the Kimi attribution debate that dogged Composer 2 stops mattering — because the next model won't need the base. The transparency concession Aman Sanger made about under-disclosing Kimi on Composer 2 ^[5]reads less like an apology and more like a tidying-up before the room is no longer relevant.