Accidentally editing old chat message wipes context after

Support Bug Reports
, ,
1

Where does the bug appear (feature/product)?

Cloud Agent (GitHub, Slack, Web, Linear)

Describe the Bug

I accidentally pressed enter while reading an old chat message I sent. I had no idea cursor’s default was to delete all of what comes after. I simply was ctrl+f searching through the chat history (enter is the keyboard shortcut to go to next) and forgot to click out of the message box before going to the next match.

Steps to Reproduce

  1. Create a chat in the agents window.
  2. Talk for a long time.
  3. Click an old message you sent in order to read the whole thing.
  4. Accidentally press enter (which also happens to be the “find next” shortcut in the agents window).
  5. Lose hours of conversation that occur after that message.

Expected Behavior

Cursor should either:

  • fork the conversation
  • ask me if I’m sure I want to lose hours of conversation that comes after

Operating System

MacOS

Version Information

Version: 3.18.25
VS Code Extension API: 1.128.0
Commit: 280eca2911f1774689696e5f1efa5a4f97a87af0
Date: 2026-08-31T23:08:02.261Z
Layout: Agent Window
Build Type: Stable
Release Track: Default
Electron: 40.10.3
Chromium: 144.0.7559.236
Node.js: 24.15.0
V8: 14.4.258.32-electron.0
xterm.js: 6.1.0-beta.291
OS: Darwin arm64 25.3.0

For AI issues: which model did you use?

GPT-5.6 Sol High

Does this stop you from using Cursor

No - Cursor works, but with this issue

3

Hi @Shawn_Jones Thanks for the post. This is actually intended behavior.

What you’re seeing is how editing a previous message works. Clicking one of your earlier messages opens it for editing, and Enter submits that edit. The conversation then continues from that point, and the messages after it are replaced. That way, the agent answers the edited prompt, instead of keeping later turns that no longer match it.

If you want to keep the existing conversation and try a different direction, fork the chat first, then edit the message on the fork. Fork is in the agent menu. While you’re searching the transcript, click out of the message, or press Escape to leave edit mode, before using Enter to jump to the next match.

4

That makes sense, although it seems like this should be harder to do on accident :grimacing:

Sounds like this is not a bug though, so I’ll just leave you with that feedback :slight_smile: