Industry Insights 11 min read

How Composer 2’s Hidden Kimi K2.5 Model Fueled a 48‑Hour AI Licensing Showdown

Within 48 hours of Cursor’s Composer 2 launch, a developer uncovered the hidden Kimi K2.5 model ID, sparking a public dispute over Modified MIT license compliance that ended in a public reconciliation and raised broader questions about open‑source AI attribution.

AI Explorer
AI Explorer
AI Explorer
How Composer 2’s Hidden Kimi K2.5 Model Fueled a 48‑Hour AI Licensing Showdown

On March 19, 2026, Cursor (parent company Anysphere, valued at $29.3 billion) released Composer 2, promoting it as a self‑developed AI coding model. Hours later, developer @fynnso discovered the internal model identifier accounts/anysphere/models/kimi-k2p5-rl-0317-s515-fast, which explicitly references Moonshot AI’s Kimi K2.5 base model.

The identifier breaks down as follows:

anysphere – Cursor’s parent company

kimi-k2p5 – Kimi K2.5 base model

rl – reinforcement‑learning fine‑tuning

0317 – training date (March 17, 2026)

s515 – internal version

fast – inference‑optimized variant

Community analysis confirmed that Composer 2’s tokenizer is identical to Kimi’s, indicating that the base model was directly used. The Kimi K2.5 model is released under a Modified MIT License that requires any commercial product with over 100 million monthly active users or $20 million monthly revenue to prominently display “Kimi K2.5” in the user interface.

Cursor’s ARR exceeds $2 billion (approximately $167 million monthly), surpassing the license threshold eightfold, yet Composer 2’s UI showed no attribution. Moonshot AI’s pre‑training lead, Yulun Du, publicly questioned Cursor on X, demanding license compliance and payment.

Cursor’s co‑founder Lee Robinson responded, acknowledging the open‑source base and stating that roughly one‑quarter of the final model’s compute originates from Kimi K2.5, with the remainder from proprietary training. He explained compliance is handled through an inference partnership with Fireworks AI.

Subsequent statements from both parties clarified the settlement: Cursor admitted using Kimi K2.5, Moonshot confirmed compliance via the Fireworks partnership, and Cursor pledged future transparency about model bases. Moonshot’s official account later posted a proud endorsement of Kimi K2.5’s role.

The episode highlights a deeper industry dilemma: when open‑source models are incorporated, fine‑tuned, and re‑branded, how should attribution and value sharing be governed? Discussions surfaced around double standards in licensing scrutiny, the significance of the “1/4 vs 4/4” compute contribution debate, and the broader need for clear norms around open‑source AI commercialization.

Full timeline:

2026‑01‑27 – Moonshot releases Kimi K2.5 under Modified MIT License

2026‑03‑17 – Cursor completes RL training on Kimi K2.5 (date embedded in model ID)

2026‑03‑19 – Composer 2 launched without mentioning Kimi K2.5

2026‑03‑19 (hours later) – @fynnso exposes model ID

2026‑03‑20 – Yulun Du publicly challenges Cursor on X

2026‑03‑20 – Cursor acknowledges open‑source base and cites Fireworks AI compliance

2026‑03‑20‑21 – Moonshot issues positive statement, both sides reconcile

AI industryCursorOpen-source licensingKimi K2.5AI model compliance
AI Explorer
Written by

AI Explorer

Stay on track with the blogger and advance together in the AI era.

0 followers
Reader feedback

How this landed with the community

Sign in to like

Rate this article

Was this worth your time?

Sign in to rate
Discussion

0 Comments

Thoughtful readers leave field notes, pushback, and hard-won operational detail here.