Agent "Changes" panel stays empty while git status shows changes

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Actual:
Agent > Local > Changes stays empty (“No Local Changes”), even when the repository has many modified/untracked files.
In some cases it also shows “Initialize Repository” although .git exists and the repo is valid.

Steps to Reproduce

  1. Open a valid Git repository in Cursor (with .git present).
  2. Make file edits (or let the agent edit files).
  3. In terminal, run git status --short and confirm modified/untracked files exist.
  4. Open Agent panel > Local > Changes.
  5. Observe that Changes stays empty.

Notes:

  • Reproduced on multiple projects.
  • git rev-parse --show-toplevel points to the correct repo.
  • git rev-parse --git-dir and --git-common-dir both return .git.
  • Reload Window does not fix.

Expected Behavior

Agent > Local > Changes should list the same local file changes detected by Git (at least equivalent to git status).
It should not show “No Local Changes” or “Initialize Repository” when the current folder is already a valid Git repository with pending changes.

Screenshots / Screen Recordings

Operating System

MacOS

Version Information

Version: 3.2.0-pre.32.patch.0
VSCode Version: 1.105.1
Commit: a35c6137b003856e0beea5591910c649f5e97350
Date: 2026-04-16T05:58:50.114Z
Layout: glass
Build Type: Stable
Release Track: Nightly
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
OS: Darwin arm64 25.5.0

For AI issues: which model did you use?

Issue is in Agent UI (“Local > Changes”), not in model output quality. Reproduced across projects.

Does this stop you from using Cursor

No - Cursor works, but with this issue

Hey, thanks for the detailed report with all the diagnostic data.

This is a known bug in the Glass layout. The Changes panel sometimes gets out of sync with the real git state and shows No Local Changes or Initialize Repository even when there are changes. A few users have hit variations of this issue:

The team is aware of it, and your report helps with prioritization.

Let me know if you notice any more details about the pattern of when this happens, like after specific agent actions.

Hey all!

Please let us know if this issue persists in 3.3.