claude-code - 💡(How to fix) Fix [FEATURE] VS Code Extension should warn when reading/writing unsaved files or use unsaved version [1 participants]

When Claude Code edits a file that has unsaved changes in the editor, it should either warn the user before proceeding or, ideally, read/edit the in-memory buffer rather than the on-disk version.

TL;DR

Implement a feature to detect unsaved changes in the editor and either warn the user or read from the in-memory buffer before Claude Code edits a file.

Guidance

• Investigate the editor's API to see if it provides a way to detect unsaved changes or access the in-memory buffer.
• Consider adding a warning prompt to alert the user of potential conflicts when Claude Code attempts to edit a file with unsaved changes.
• Look into implementing a mechanism to read from the in-memory buffer instead of the on-disk version to avoid overwriting unsaved changes.
• Evaluate the trade-offs between warning the user and automatically reading from the in-memory buffer, considering factors like user experience and potential data loss.

Notes

The implementation details will depend on the specific editor being used and its API capabilities. It's essential to weigh the benefits of this feature against potential complexities and edge cases.

Recommendation

Apply a workaround by adding a warning prompt to alert the user of potential conflicts when Claude Code attempts to edit a file with unsaved changes, as this seems to be a more straightforward solution to implement initially.