# Composer chat gets deleted and history not saved if you ctrl + backspace too far

**URL:** <https://forum.cursor.com/t/composer-chat-gets-deleted-and-history-not-saved-if-you-ctrl-backspace-too-far/22586>\
**Category:** Bug Reports\
**Created:** [October 12, 2024, 9:22pm UTC](https://forum.cursor.com/t/composer-chat-gets-deleted-and-history-not-saved-if-you-ctrl-backspace-too-far/22586 "2024-10-12T21:22:57Z")\
**Posts on this page:** 19\
**Page:** 1

<div class="post-metadata">

**Author:** ![pfapp](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/pfapp/32/5528_2.png) [@pfapp](https://forum.cursor.com/u/pfapp)\
**Post date:** [October 12, 2024, 9:22pm UTC](https://forum.cursor.com/t/composer-chat-gets-deleted-and-history-not-saved-if-you-ctrl-backspace-too-far/22586/1 "2024-10-12T21:22:57Z")

</div>

happened to multiple times in the last 24 hours.

I’ll be revising a prompt and if you ctrl back space after theres no text, it removes files, then deletes composer chat and theres no history.

---

<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:** [October 13, 2024, 11:05am UTC](https://forum.cursor.com/t/composer-chat-gets-deleted-and-history-not-saved-if-you-ctrl-backspace-too-far/22586/2 "2024-10-13T11:05:59Z")

</div>

Hi @pfapp

Which version of Cursor are you using?

---

<div class="post-metadata">

**Author:** ![HedgedAndLevered](https://avatars.discourse-cdn.com/v4/letter/h/a4c791/32.png) [@HedgedAndLevered](https://forum.cursor.com/u/HedgedAndLevered)\
**Post date:** [October 13, 2024, 3:19pm UTC](https://forum.cursor.com/t/composer-chat-gets-deleted-and-history-not-saved-if-you-ctrl-backspace-too-far/22586/3 "2024-10-13T15:19:02Z")

</div>

Same thing happened to me yesterday. I’m not sure whether it was before or after I upgraded from 41.3 to 42

---

<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:** [October 13, 2024, 4:24pm UTC](https://forum.cursor.com/t/composer-chat-gets-deleted-and-history-not-saved-if-you-ctrl-backspace-too-far/22586/4 "2024-10-13T16:24:19Z")

</div>

This shortcut is meant for rejecting all.

![image](https://us1.discourse-cdn.com/cursor1/original/2X/c/c03007707dafc249c37ef7f137e6d22f9759dabc.png)

---

<div class="post-metadata">

**Author:** ![HedgedAndLevered](https://avatars.discourse-cdn.com/v4/letter/h/a4c791/32.png) [@HedgedAndLevered](https://forum.cursor.com/u/HedgedAndLevered)\
**Post date:** [October 13, 2024, 4:52pm UTC](https://forum.cursor.com/t/composer-chat-gets-deleted-and-history-not-saved-if-you-ctrl-backspace-too-far/22586/5 "2024-10-13T16:52:05Z")

</div>

control+delete is extremely commonly used in everyday coding and should not be a default shortcut to do something else, especially for any kind of “apply all”, especially one that isnt eligible for undo, imo

---

<div class="post-metadata">

**Author:** ![Flo](https://avatars.discourse-cdn.com/v4/letter/f/b38774/32.png) [@Flo](https://forum.cursor.com/u/Flo)\
**Post date:** [October 13, 2024, 5:17pm UTC](https://forum.cursor.com/t/composer-chat-gets-deleted-and-history-not-saved-if-you-ctrl-backspace-too-far/22586/6 "2024-10-13T17:17:02Z")

</div>

- 
  - 
    - Highly Note \* \* \*

It is indeed extremely annoying when the chat is constantly deleted by the composer. Consider how important aspects of prompt creation and the most recently sent data can endanger your own project. Please, dear @anon-9002714 team, take this very seriously.

I strongly recommend a backup cloud function, where even with the backup cloud function the user has the option of setting a secondary function for the saved chats to block them in order to prevent them from being accidentally deleted.

This provides a significant guarantee and satisfaction for everyone.

---

<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:** [October 14, 2024, 4:39pm UTC](https://forum.cursor.com/t/composer-chat-gets-deleted-and-history-not-saved-if-you-ctrl-backspace-too-far/22586/7 "2024-10-14T16:39:53Z")

</div>

I checked this in Cursor 0.42.2, and the history is saved even if you clicked “Reject All.”

---

<div class="post-metadata">

**Author:** ![pfapp](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/pfapp/32/5528_2.png) [@pfapp](https://forum.cursor.com/u/pfapp)\
**Post date:** [October 14, 2024, 10:11pm UTC](https://forum.cursor.com/t/composer-chat-gets-deleted-and-history-not-saved-if-you-ctrl-backspace-too-far/22586/8 "2024-10-14T22:11:32Z")

</div>

I have composer persistence ticked on

using latest version of cursor

still getting a total deletion of the entire composer conversation if you ctrl + backspace when there isn’t text in the composer chat.

I understand you are using ctrl + backspace to reject all but please don’t allow it to also delete the entire conversation. I have a video to show you what I mean if its not clear

---

<div class="post-metadata">

**Author:** ![pfapp](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/pfapp/32/5528_2.png) [@pfapp](https://forum.cursor.com/u/pfapp)\
**Post date:** [October 14, 2024, 10:12pm UTC](https://forum.cursor.com/t/composer-chat-gets-deleted-and-history-not-saved-if-you-ctrl-backspace-too-far/22586/9 "2024-10-14T22:12:17Z")

</div>

what happens when you ctrl + backspace in a composer window that has multiple linked files?

---

<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:** [October 15, 2024, 7:55am UTC](https://forum.cursor.com/t/composer-chat-gets-deleted-and-history-not-saved-if-you-ctrl-backspace-too-far/22586/10 "2024-10-15T07:55:40Z")

</div>

Please share the video.

---

<div class="post-metadata">

**Author:** ![pfapp](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/pfapp/32/5528_2.png) [@pfapp](https://forum.cursor.com/u/pfapp)\
**Post date:** [October 15, 2024, 11:43pm UTC](https://forum.cursor.com/t/composer-chat-gets-deleted-and-history-not-saved-if-you-ctrl-backspace-too-far/22586/11 "2024-10-15T23:43:37Z")

</div>



---

<div class="post-metadata">

**Author:** ![balta](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/balta/32/8389_2.png) [@balta](https://forum.cursor.com/u/balta)\
**Post date:** [October 16, 2024, 12:17am UTC](https://forum.cursor.com/t/composer-chat-gets-deleted-and-history-not-saved-if-you-ctrl-backspace-too-far/22586/12 "2024-10-16T00:17:33Z")

</div>

hi pfapp, if you do command backspace on an empty input box, we reset your composer. if you do this by accident, you can do cmd-z on the input box to undo this reset. hope this helps!

---

<div class="post-metadata">

**Author:** ![nekoboxcoder](https://avatars.discourse-cdn.com/v4/letter/n/e9bcb4/32.png) [@nekoboxcoder](https://forum.cursor.com/u/nekoboxcoder)\
**Post date:** [October 28, 2024, 11:06am UTC](https://forum.cursor.com/t/composer-chat-gets-deleted-and-history-not-saved-if-you-ctrl-backspace-too-far/22586/13 "2024-10-28T11:06:16Z")

</div>

I agree with everyone here. I use `Ctrl-backspace` extensively for deleting words quickly. I lost the whole history of the composer and now too late to find out that `ctrl-z` can undo it.

This literally acts as deleting your composer conversation history unless people see this post and know `ctrl-z` to revert. This shouldn’t be default at all, even if it is there should be a prompt to avoid this happening accidentally

---

<div class="post-metadata">

**Author:** ![stimpy77](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/stimpy77/32/10597_2.png) [@stimpy77](https://forum.cursor.com/u/stimpy77)\
**Post date:** [November 2, 2024, 4:36pm UTC](https://forum.cursor.com/t/composer-chat-gets-deleted-and-history-not-saved-if-you-ctrl-backspace-too-far/22586/14 "2024-11-02T16:36:32Z")

</div>

Thanks for sharing about ctrl-z. Now that I know this it was too late for me, too. Ugh.

---

<div class="post-metadata">

**Author:** ![codymtaylor](https://avatars.discourse-cdn.com/v4/letter/c/d6d6ee/32.png) [@codymtaylor](https://forum.cursor.com/u/codymtaylor)\
**Post date:** [November 14, 2024, 5:09pm UTC](https://forum.cursor.com/t/composer-chat-gets-deleted-and-history-not-saved-if-you-ctrl-backspace-too-far/22586/15 "2024-11-14T17:09:23Z")

</div>

I agree with others, ctrl+z is nice (if you know it) but deleting the entire composer should not be the default behavior at all. This has burned me multiple times. Please remove it!

Deleting a whole composer is a drastic step and the user should have to take significant action to make it happen (e.g. open control panel, click delete icon), not just normal keystrokes in the text field.

---

<div class="post-metadata">

**Author:** ![cheul](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/cheul/32/12478_2.png) [@cheul](https://forum.cursor.com/u/cheul)\
**Post date:** [November 20, 2024, 3:16pm UTC](https://forum.cursor.com/t/composer-chat-gets-deleted-and-history-not-saved-if-you-ctrl-backspace-too-far/22586/16 "2024-11-20T15:16:46Z")

</div>

why such an extreme action (deleting entire composer history so far) is mapped to a command that is used so often? it is just terrible choice of interaction design

---

<div class="post-metadata">

**Author:** ![stimpy77](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/stimpy77/32/10597_2.png) [@stimpy77](https://forum.cursor.com/u/stimpy77)\
**Post date:** [March 20, 2025, 5:31pm UTC](https://forum.cursor.com/t/composer-chat-gets-deleted-and-history-not-saved-if-you-ctrl-backspace-too-far/22586/17 "2025-03-20T17:31:18Z")

</div>

I’m digging this up again. Clearly Cursor’s dev team doesn’t use ctrl+backspace like some of us but I use ctrl+backspace more than I use just plain backspace when I type. There is nothing more horrifying than to see progress utterly obliterated just because I’m typing “Hey that’s greta” and then try to clean up that word.  
I’ve glad that I can go in and remove keybindings but I’ve had to do that. There are so many of them 😢  
This is an issue now in current Cursor with integrated agent, as the last previously approved changes from the last interaction are suddenly rolled back.

---

<div class="post-metadata">

**Author:** ![dmschlot](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/dmschlot/32/35362_2.png) [@dmschlot](https://forum.cursor.com/u/dmschlot)\
**Post date:** [March 24, 2025, 8:41pm UTC](https://forum.cursor.com/t/composer-chat-gets-deleted-and-history-not-saved-if-you-ctrl-backspace-too-far/22586/18 "2025-03-24T20:41:21Z")

</div>

I ran into the same issue and was able to fix it by changing the shortcut for “Cursor: Cancel Composer” to something much harder to hit by accident. I used `Ctrl+Shift+Alt+Backspace`

Just to share why it’s so frustrating: I’ll often have an AI agent generate and modify a large chunk of code—sometimes 30+ files. Then while I’m typing a follow-up prompt, I instinctively hit `Ctrl+Backspace` (which deletes the last word on Windows). But that default shortcut cancels the whole composer, wiping out all that work. You _can_ reapply each change individually, but with 30+ edits and the interface jumping back to the top of the list every time, it’s a huge time sink.

Hope this helps others.

Thanks

---

<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:** [December 21, 2025, 8:57am UTC](https://forum.cursor.com/t/composer-chat-gets-deleted-and-history-not-saved-if-you-ctrl-backspace-too-far/22586/19 "2025-12-21T08:57:42Z")

</div>

Closed on December 21, 2025, 8:57am UTC

This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.
