Cursor releases Composer 2.5

Cursor released Composer 2.5 on May 18, 2026, as the latest version of its in-house coding model, according to the company’s changelog and blog. The update was published one day before broader discussion spread on X on May 19, including a roundup post that pointed users to the release. Cursor described the model as an upgrade to Composer 2 aimed at longer-running software tasks, more reliable instruction-following and better collaboration behavior. The company also attached new pricing and a temporary usage promotion to the launch. ### When did Cursor actually ship Composer 2.5? May 18 is the date Cursor itself attached to the release. The company’s changelog says “Composer 2.5 is now available in Cursor,” and its blog index lists an “Introducing Composer 2.5” post dated the same day. A May 19 social-media roundup then amplified the launch, which appears to be the source of some secondary references to May 19 rather than May 18. (cursor.com) May 19 also brought follow-up discussion on Cursor’s own community forum. The forum shows an announcement thread titled “Composer 2.5 is now live!” dated May 18, followed by May 19 discussion threads inviting user feedback and advertising a one-day increase in usage. ### What did Cursor say changed in Composer 2.5? Cursor said Composer 2.5 is “a substantial improvement in intelligence and behavior over Composer 2.” The changelog says the model is “better at sustained work on long-running tasks,” “follows complex instructions more reliably,” and is “more pleasant to collaborate with.” Those are the clearest first-party claims attached to the launch. (cursor.com) Cursor’s public site also places Composer 2.5 prominently in the product interface alongside agent features, showing it as the model used for command-style software-building tasks inside Cursor. (forum.cursor.com) The homepage says agents using Composer 2.5 can work autonomously, run in parallel, and build, test and demo features for review. ### How was the model priced at launch? Cursor kept the standard Composer 2.5 price at $0.50 per million input tokens and $2.50 per million output tokens, according to the changelog. (cursor.com) The company listed a faster default tier at $3.00 per million input tokens and $15.00 per million output tokens. Cursor also said Composer 2.5 would include double usage for the first week and directed users to its model documentation for details. (cursor.com) March 19 pricing for Composer 2 provides a comparison point. Cursor had priced Composer 2 at the same standard rate, but its faster default tier was lower at $1.50 per million input tokens and $7.50 per million output tokens, according to the earlier changelog entry. ### How does this fit into Cursor’s recent product cycle? March 19 was the date Cursor introduced Composer 2, describing it as a frontier-level coding model with strong CursorBench results and higher token efficiency. (cursor.com) February 9 was the date for Composer 1.5, which Cursor said balanced speed and intelligence for daily use. The May 18 Composer 2.5 release continues that rapid sequence of model updates inside the company’s coding product. (cursor.com) May 19 also brought another product release from Cursor: a Jira integration that lets teams assign work items to Cursor or mention “@Cursor” in comments to start a cloud agent. That places Composer 2.5 inside a broader week of product changes around agents and developer workflow. ### Where can developers see the next details? Cursor’s changelog says users can read more in the company’s announcement and consult model documentation for full details. (cursor.com) The company’s community forum also shows active May 19 discussion threads for Composer 2.5 feedback and promotional usage changes, which are likely to be the next public venues for rollout specifics and user response. (cursor.com)