# Losing Changes by accidentally exiting/resetting composer

**URL:** <https://forum.cursor.com/t/losing-changes-by-accidentally-exiting-resetting-composer/18967>\
**Category:** Feedback\
**Created:** [September 26, 2024, 2:11pm UTC](https://forum.cursor.com/t/losing-changes-by-accidentally-exiting-resetting-composer/18967 "2024-09-26T14:11:50Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![jonathanwmaddison](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/jonathanwmaddison/32/6409_2.png) [@jonathanwmaddison](https://forum.cursor.com/u/jonathanwmaddison)\
**Post date:** [September 26, 2024, 2:11pm UTC](https://forum.cursor.com/t/losing-changes-by-accidentally-exiting-resetting-composer/18967/1 "2024-09-26T14:11:50Z")

</div>

I think this creates a terrible UX. I have accidentally/unknowingly lost an hour or two of changes by closing/resetting the compose without accepting all. There needs to be some modal or warning that you are going to lose all of the compose changes. After a longer compose session, there are sometimes changes I want to keep but the compose session starts failing/getting wonky so I want a fresh start. If I forget to ‘accept all’ then I lose everything.

This is confusing UX and I think saving changes should not be undone unless we very explicitly tell cursor to UNDO all with a very explicit warning that you are going to lose changes.

---

<div class="post-metadata">

**Author:** ![deanrie](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/deanrie/32/1263_2.png) [@deanrie](https://forum.cursor.com/u/deanrie)\
**Post date:** [September 26, 2024, 2:38pm UTC](https://forum.cursor.com/t/losing-changes-by-accidentally-exiting-resetting-composer/18967/2 "2024-09-26T14:38:39Z")

</div>

Hi @jonathanwmaddison

Are you referring to Composer? Yeah, I’ve encountered that a few times myself. Thanks for sharing, I’ll keep it in mind.

---

<div class="post-metadata">

**Author:** ![jonathanwmaddison](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/jonathanwmaddison/32/6409_2.png) [@jonathanwmaddison](https://forum.cursor.com/u/jonathanwmaddison)\
**Post date:** [September 26, 2024, 5:08pm UTC](https://forum.cursor.com/t/losing-changes-by-accidentally-exiting-resetting-composer/18967/3 "2024-09-26T17:08:37Z")

</div>

Yes exactly – the composer.

---

<div class="post-metadata">

**Author:** ![paradev](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/paradev/32/6988_2.png) [@paradev](https://forum.cursor.com/u/paradev)\
**Post date:** [September 27, 2024, 10:52pm UTC](https://forum.cursor.com/t/losing-changes-by-accidentally-exiting-resetting-composer/18967/4 "2024-09-27T22:52:59Z")

</div>

Right. To fix some of the context issues, I have to close and reopen Cursor, but I also don’t understand why Composer loses all history and there doesn’t seem to be a way to retain it.

---

<div class="post-metadata">

**Author:** ![system](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/system/32/99069_2.png) [@system](https://forum.cursor.com/u/system)\
**Post date:** [June 18, 2026, 10:16am UTC](https://forum.cursor.com/t/losing-changes-by-accidentally-exiting-resetting-composer/18967/5 "2026-06-18T10:16:57Z")

</div>

Closed on June 18, 2026, 10:16am UTC