# Clarification on Composer 1 retirement (March 16 migration email)

**URL:** <https://forum.cursor.com/t/clarification-on-composer-1-retirement-march-16-migration-email/154239>\
**Category:** Help\
**Tags:** composer\
**Created:** [March 10, 2026, 7:20am UTC](https://forum.cursor.com/t/clarification-on-composer-1-retirement-march-16-migration-email/154239 "2026-03-10T07:20:00Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![mohitjain](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/mohitjain/32/100229_2.png) [@mohitjain](https://forum.cursor.com/u/mohitjain)\
**Post date:** [March 12, 2026, 10:24am UTC](https://forum.cursor.com/t/clarification-on-composer-1-retirement-march-16-migration-email/154239/3 "2026-03-12T10:24:34Z")

</div>

Hi Simon,

Composer 1 will be completely retired on March 16, 2026, it will no longer be available as a selectable model on any plan. As the email states, the capacity is being reallocated to serve Composer 1.5, so Composer 1 will not remain available in any form after that date.

All users currently using Composer 1 will be automatically moved to Composer 1.5, which draws from the Auto + Composer usage pool and includes significantly more usage.

Let me know if you have any other questions!

Best,  
Mohit

---

_[View the full topic](https://forum.cursor.com/t/clarification-on-composer-1-retirement-march-16-migration-email/154239)._