Stale git snapshots in new agent chats

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

I’m having this exact issue. Cursor Cache Issues, Context issue

When I don’t like an agents work, I try it again with a different model. Suddenly that’s broken. New agent chats suddenly started using files created by previous agent chats, with a completely clean working directory. I asked the agent and it said it was initialized with a stale git snapshot. The two possibilities suggested in reply to the linked issue seem to be both mistaken ignore what that previous issue said.

  1. I’m using a different model, so its not model determinism.
  2. working directory is definitely clean, no untracked files, nothing in git clean -nd

I keep opening new agent tabs, in the sidebar with the + sign. and it keeps having a stale git snapshot, even though I cleaned my git before opening the tab. Retrying agent builds is part of my basic workflow, so really need a way to get clean agents.

Thanks for your help

Steps to Reproduce

  1. Open agent and ask to write code files
  2. Undo all changes, and delete all newly created files
  3. Ask agent about old files, it will mention specific details, and say it can see them in git snapshot

Expected Behavior

Clean context when starting new agent.

Operating System

MacOS

Version Information

Version: 3.15.6
VS Code Extension API: 1.128.0
Commit: a1f686545fd0ce8917bbd2449f733551a9bce420
Date: 2026-08-06T01:41:03.876Z
Layout: IDE
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 24.6.0

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

5

Fixed by restarting the app.

7

Hey @Eliyahu_Block - glad the restart cleared it. If it happens again after a big cleanup, reload the window (or restart) before opening a new Agent tab, or ask the new agent to run git status first. Related: <git_status> system prompt stale in new AI chat. This is an issue we’re tracking.