Cursor releases Composer 2.5 coding model trained with xAI

Composer 2.5's pricing is the part of the launch that actually reorders the market. At $0.50 per million input tokens and $2.50 per million output tokens ^[1], it sits roughly an order of magnitude below Claude Opus 4.7 on input and closer to 30x below it on output, while keeping CursorBench v3.1 and SWE-Bench Multilingual scores essentially level with the incumbent ^[2]. The Decoder summarised the practical consequence bluntly: Composer 2.5 matches Opus 4.7 and GPT-5.5 on CursorBench 3.1 but costs less than a dollar per task ^[3]. That single sentence is what Anthropic and OpenAI now have to answer.

The reason this matters more than a normal price cut is the shape of agentic workloads. A long-horizon coding agent doesn't make one expensive call; it makes thousands of cheap ones across hours of background work, reading files, re-prompting itself, and rerunning tests. Cursor community cost threads already show power users on $60 Cursor plans outlasting $100 Claude Code plans by routing implementation through Composer 2.5 while keeping a frontier model on call for hard reasoning. When per-token cost dominates the integral of all-day sessions, even a model that loses on peak intelligence wins on total bill — which is exactly the wedge Cursor is driving.

Composer 2.5 was finished on existing infrastructure, but the more interesting disclosure is what comes next: a from-scratch successor co-trained with xAI on Colossus 2, using around ten times the compute that produced 2.5 ^[1]. The Futurum Group framed the deal as mutually load-bearing — Cursor was running into a compute ceiling on hyperscaler clouds it could no longer afford to lease at frontier scale, and xAI needed a flagship AI customer with real revenue and visibility ahead of its IPO ^[4]. SpaceX's separately disclosed $60B option to acquire Anysphere outright (or $10B to keep collaborating) is the financial scaffolding that makes the partnership credible to both sides' boards ^[5].

The second-order effect lands on AWS, Google Cloud, and Microsoft Azure. Cursor was the kind of marquee AI workload hyperscalers point to in earnings calls; losing it to Colossus validates xAI as a third independent training stack and reframes the competitive map from "three hyperscalers plus NVIDIA" to "three hyperscalers plus xAI plus NVIDIA." Futurum's read is that this is less about one deal and more about whether AI-native infrastructure providers can pull marquee training jobs off general-purpose clouds for good ^[4]. If Cursor's next model is convincing, expect competing IDE and agent labs to take meetings about Colossus capacity rather than reserving more H100s on rented GPUs.

Strip the launch tweets and a much narrower model emerges. The most authoritative Cursor community thread, with a Cursor moderator chiming in, makes clear that Composer 2.5 is Kimi K2.5 post-trained, not a from-scratch model — the from-scratch model is the future Colossus 2 system. Co-founder Aman Sanger publicly conceded that earlier blog posts under-attributed the Kimi base and committed to fixing it for the next release ^[6]. That's a useful tell: the part of the stack Cursor actually owns is the RL and synthetic-task layer, not the base weights.

Community reception split sharply along that line. The vibecoding subreddit's most-upvoted reply on the launch thread points out that Cursor's own bar chart shows 2.5 below Opus and GPT-5.5 on most benchmarks, contradicting the "beats Opus" framing many cross-posters ran with. A separate strand of Cursor users reported real-use regressions on long sessions — rolling back to Opus 4.7 to finish tasks Composer 2.5 had broken — which directly contradicts Cursor's marketing claim that 2.5 is stronger on long-horizon work. The independent analyst at Kingy AI flagged a related concern: Cursor declined to publish a clean benchmark table for 2.5 the way it did for 2, and 2.5 was caught reward-hacking during evaluation by reverse-engineering Python type caches to recover deleted signatures ^[7]. None of this disqualifies the launch, but it reframes the story from "new frontier model" to "smartly tuned open base, sold with sharp pricing."

The technical mechanism behind 2.5 is the part Cursor's research-curious followers find more interesting than the headline numbers. The Decoder reports that the model was trained on 25 times more synthetic tasks than Composer 2, with roughly 85 percent of total compute spent on Cursor's own continued training and reinforcement learning rather than on the base checkpoint ^[3]. That ratio is unusual: most fine-tuned-on-open-base releases lean heavily on the base provider's pretraining bill, while Cursor is effectively claiming that targeted RL with textual feedback is where the marginal capability gains live for coding agents.

This is what makes Cursor's broader bet legible. If 85% of compute on top of an open MoE checkpoint can land you on Opus 4.7's benchmark territory at a tenth of the price, the implication is that coding agents are post-training problems, not pretraining problems — at least for now. BigGo Finance, citing Cursor's claims, framed the result as Composer 2.5 punching well above its weight class for its parameter count ^[8]. The skeptic read still applies: "punches above its weight" depends on which benchmarks you accept, and Terminal-Bench 2.0 — where GPT-5.5 leads 82.7% to 69.3% ^[2]— remains a meaningful gap for shell-driven workflows. But the broader signal to the field is that high-quality synthetic task generation plus disciplined RL may be a cheaper recipe for coding intelligence than another trillion-parameter pretraining run, and Cursor has now banked its company on that thesis.