On March 19, 2026, US AI coding tool Cursor (parent company Anysphere, valued at approximately $29.3 billion) publicly released its in‑house model Composer 2. The official blog described it as "frontier‑level coding intelligence," claiming it significantly outperformed Claude Opus 4.6 on benchmarks such as Terminal‑Bench 2.0 and SWE‑bench Multilingual, and priced it at just $0.50 per million input tokens and $2.50 per million output tokens (fast tier by default), far below comparable flagship models. Cursor attributed the performance gains to "continued pretraining + high‑compute reinforcement learning (RL)," without mentioning any external base model.
However, just two hours after the release, developer @fynnso captured API traffic and discovered the model ID was kimi‑k2p5‑rl‑0317‑s515‑fast. The finding instantly ignited the web: Composer 2's tokenizer matched Moonshot AI's Kimi K2.5 exactly, prompting accusations of "repackaging" an open‑source model without attribution or payment. The controversy spread rapidly; Elon Musk personally commented: "Yes, this is Kimi 2.5." For a time, claims of "Cursor repackaging Chinese open source" and "a US big company freeloading Kimi" trended across X, Hacker News and domestic communities.
Background: Cursor's 'In‑House' Ambition and a Pricing Shock
Cursor, an AI code editor with millions of daily active users, positioned Composer 2 as a "self‑developed frontier model." The company claimed scores of 61.3 on CursorBench and 61.7 on Terminal‑Bench 2.0 (surpassing Claude Opus 4.6's 58.0), and touted Agentic capabilities including multi‑file editing, terminal operations and browser control. The pricing was described as "nuclear": roughly one‑fifth to one‑sixth of GPT‑5.4 and one‑tenth of Claude Opus 4.6's price, earning praise from developers as a "best value" coding model.
But the gloss was quickly pierced by technical detail. Moonshot's pretraining lead Yulun Du posted that the model's characteristics highly overlapped with Kimi K2.5 and that the tokenizer was identical, saying it was "almost certain to be our model further fine‑tuned." He directly asked Cursor's co‑founder: "Why did you not respect our license, and why was no payment made?"
Climax: Musk Weighs In and the Internet Watches
Hours into the dispute, Elon Musk publicly confirmed the base was Kimi 2.5, pushing the story to a climax. Hacker News, Reddit r/cursor, Bilibili and Weibo became hubs for commentary. Some accused Cursor of "a US company stealing Chinese open source," and questioned whether its roughly $29.3 billion valuation was built on "repackaged open source." Cursor had previously faced scrutiny when Composer 1 was exposed as based on Qwen, so the pressure was extraordinary.
Reversal: Moonshot Clarifies an Authorized Collaboration
Just as the situation threatened to spiral, Moonshot's official account @Kimi_Moonshot posted a long statement the evening of March 20, shifting tone from challenge to congratulations: "Congratulations to the Cursor team on releasing Composer 2! We are proud to see Kimi‑k2.5 providing the foundation... this is the open model ecosystem working as we hope."
Key clarifications:
- Cursor accessed Kimi K2.5 commercially through Fireworks AI (an inference and RL hosting platform founded by former Meta PyTorch members, valued at $4 billion), constituting an authorized commercial collaboration.
- Fireworks handled license compliance on behalf of the parties, and Cursor performed continued pretraining and high‑intensity RL optimization at roughly four times the compute scale.
- Moonshot emphasized that the open‑source model ecosystem is meant to be integrated efficiently, and that the cooperation between the parties was fully compliant.
Cursor co‑founders Lee Robinson and Aman Sanger subsequently issued apologies: acknowledging the initial blog failed to attribute the Kimi base as an oversight and pledging that "the next model will include clear attribution." They also revealed that Kimi K2.5 showed the strongest perplexity results, that Cursor invested about one‑quarter of the compute on the base, and that the remaining three‑quarters came from their own training.
Consequences and Industry Impact
- Kimi's exposure: Moonshot, previously low‑profile, became a global focus overnight. Musk's comment plus Cursor's acknowledgment made "Kimi K2.5" a trending topic. Related Moonshot concept stocks strengthened the next day, and international recognition of a Chinese open‑source model rose markedly.
- Cursor's valuation and reputation—a double‑edged sword: Initially accused of "repackaging open source," the authorization clarification defused the crisis. Community sentiment largely shifted to recognition: "Not repackaging, but smartly standing on giants' shoulders." Nevertheless, a lesson on insufficient transparency remained.
- Open‑source ecosystem signals: The episode highlighted the blurred boundaries of permissive licenses like the MIT license in commercial contexts. Hosting platforms such as Fireworks are emerging as "bridges for open‑source commercialization." Going forward, large companies fine‑tuning open models will need clearer attribution and compliance to avoid similar PR crises.
- Acceleration in programming tools: With low price and high performance, Cursor Composer 2 remains one of 2026's most noteworthy coding agent models. The incident also pushed more developers toward either self‑development or authorized paths to avoid "black‑box" risk.
Conclusion: A New Paradigm for Open‑Source Collaboration
From a "repackaging storm" to official mutual congratulations within 24 hours, the Cursor Composer 2 episode is one of 2026's fastest "fall‑and‑reversal" cases in the AI world. It is not an infringement scandal so much as a typical story of authorized commercial collaboration under an open ecosystem: Kimi provided a strong base, Cursor applied high‑intensity RL, and Fireworks ensured compliance, producing a three‑way win.
For Moonshot, the episode marks another milestone in Chinese open‑source models going global; for Cursor, it is a lesson in transparency while growing; for the industry, it is a reminder that standing on open‑source giants' shoulders enables faster progress but requires respect for the rules and open acknowledgement.
As more similar collaborations emerge, 2026's AI development may enter a new phase of "shared bases + vertical optimization." Open source will no longer mean "free riding," but the starting point for ecosystem‑wide wins.
▶️ Enjoyed this piece? Creating content is hard!
Follow our YouTube channel:
AI Rosetta
Your likes, subscriptions and shares are our greatest support! 🙏
More AI news at: https://www.airosetta.com