File Changes Triggered When Switching Chats in Cursor

Support Bug Reports
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

There seems to be a recurring issue in Cursor across multiple versions.

When I run a local project server on my machine, and then open/close the window or switch between chats, I sometimes see a message indicating that files have changed (triggering a reload in frameworks like Django auto-reload).

The issue is that these changes are not always intentional, which makes the workflow unreliable. In some cases, it feels like files might be modified or reloaded without me explicitly editing them.

This creates uncertainty during development, especially when working on active projects.

It would be great to ensure that switching chats or navigating the UI does not interfere with file states or trigger unintended file change events.

Steps to Reproduce

…

Operating System

Windows 10/11

Version Information

Version: 3.1.15 (user setup)
VSCode Version: 1.105.1
Commit: 3a67af7b780e0bfc8d32aefa96b8ff1cb8817f80
Date: 2026-04-15T01:46:06.515Z
Layout: editor
Build Type: Stable
Release Track: Default
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
OS: Windows_NT x64 10.0.19045

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

6

Hey! This is a known issue where Cursor’s session restoration can replay old Agent/Composer inline diff states to disk, which triggers file watchers like Django’s auto-reload. Several users have reported similar behavior, and our team is actively investigating.

In the meantime, a workaround that has helped others: for each affected file, open it in Cursor, click “Keep” or “Undo” in the inline diff banner that appears, then save and discard the changes in git. Once you clear the stale diff state for a file this way, it should stop resurfacing.

You can follow along in this related thread where others have shared additional details and workarounds:

Let me know if the workaround helps or if you’re still seeing it after clearing the stale diffs!