Windsurf: Visual diffs break and become inaccessible when renaming files with pending diffs

[jeffcoughlin]

Description:
When a file that has pending (unaccepted) diffs is renamed, the visual diff display and acceptance functionality breaks for all diffs. The AI conversation and code modification capabilities remain intact, but users lose the ability to see or accept any changes being made.

Steps to Reproduce:

1. Start a conversation with the AI Assistant
2. Have the AI propose changes to a file, creating diffs
3. Before accepting all diffs for that file, rename the file
4. Try to view or accept any proposed changes

Expected Behavior:

• Visual diffs should continue to display after renaming a file with pending diffs
• Users should be able to see and accept proposed changes
• The diff system should handle file rename operations gracefully

Actual Behavior:

• Visual diffs disappear and become inaccessible
• Cannot see what changes the AI is making to files
• Cannot accept any completed changes
• The AI continues to function normally and maintains conversation context
• The AI can continue making code changes, but users cannot see what is being changed
• The issue affects all diffs, not just those in the renamed file

Technical Details:

• Only occurs when renaming files that have pending (unaccepted) diffs
• Renaming other files in the workspace does not trigger the issue
• Only affects the diff visualization and acceptance system
• The conversation context and AI functionality remain intact
• The issue persists across application restarts
• Seems to be related to how the diff system tracks file paths for pending changes

Impact:

• Users cannot verify changes before they are made
• Makes it impossible to review code modifications
• Forces users to either:
  a) Start a new conversation to regain diff visibility
  b) Blindly trust the AI's changes without visual verification

Environment:

• Windows OS, Mac OS
• Latest version of Windsurf IDE
• Affects all file types and languages
• To my knowledge, this bug has existed since the first public beta release

Workarounds:

1. Accept all diffs in a file before renaming it
2. Start a new conversation after performing rename operations on files with pending diffs
3. Document intended changes before renaming files

Additional Notes:

• The issue appears to be specifically with the diff visualization system's handling of file renames
• The AI's ability to track files and make changes remains functional
• Only the user's ability to see and accept changes is affected
• The issue is specifically tied to files that have pending diffs, not all files in the workspace

[alnimra]

Running into this same issue.

[njeanselme]

same issue