Copy and Fork buttons remain visible after rewind

Support Bug Reports
, ,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

After rewinding or editing a previous user message, the subsequent assistant turns become greyed out because they are no longer part of the active conversation branch. However, these inactive future turns still display the normal Copy Message and Fork Chat buttons.

These actions should not be presented as normal actions on turns that have already been excluded by rewind. In particular, Fork Chat is ambiguous because the displayed turn is no longer part of the active branch.

This appears to be a client-side transcript UI regression introduced in Cursor 3.17. The issue did not occur in Cursor 3.16.

Steps to Reproduce

  1. Open a local Agent conversation in Cursor IDE.
  2. Send multiple messages and receive assistant responses.
  3. Rewind the conversation by editing a previous user message.
  4. Observe the assistant turns after the rewind point.
  5. The future turns are greyed out, but their Copy Message and Fork Chat buttons remain visible and appear actionable.

Expected Behavior

Turns excluded from the active branch by rewind should not expose normal turn actions such as Copy Message and Fork Chat.

Alternatively, if retaining these actions is intentional, the UI should clearly distinguish actions targeting an inactive historical branch. The current presentation makes greyed-out turns appear partially active.

Screenshots / Screen Recordings

PixPin_2026-08-29_16-53-27.jpg
PixPin_2026-08-29_16-53-27.jpg2776×784 89.1 KB

Operating System

MacOS

Version Information

Cursor 3.18.9
Commit: 2ba48ff3f7514cc4643c52ca9f7b3173d9b66130

Regression range observed:
Cursor 3.16.29: issue not observed
Cursor 3.17.8 and later: issue observed

For AI issues: which model did you use?

Not model-specific. This is a Cursor IDE transcript UI issue and can occur independently of the selected model or provider.

For AI issues: add Request ID with privacy disabled

Not applicable. The issue occurs entirely in the client UI after rewind and is not tied to a model request.

Additional Information

The problem appears in the Agents Window transcript after rewind. It is not specific to Local Mode or a custom provider; the affected Copy/Fork controls are rendered by the Cursor client.

The regression appears related to inactive future turns retaining the same actions as active turns after the transcript UI changes introduced in Cursor 3.17.

I could not find an existing public Cursor Forum report describing this exact issue.

Does this stop you from using Cursor

No - Cursor works, but with this issue

5

Hey, thanks for the detailed report with the regression range and the screenshot.

You’re right. After rewinding, turns that are no longer in the active branch still show Copy Message and Fork Chat in the normal style, so they look partially active. I agree the UI is confusing here. I’ve passed this to the team so they can fix how these actions look on inactive turns. I can’t share a timeline yet, but I’ll post an update here if I get one.

For now, the actions themselves work as expected. Copy copies the content of that message, and Fork Chat creates a new chat branched from that point, which is a handy way to continue from the part of the conversation you rewound to.