Git changes not appear for remote sessions

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

When I open up the new Cursor agents window and use a workspace from another machine, during the SSH authentication step the git changes tab fails and does not recover “Failed to load changes”. It fails before I can even authenticate into the workspace.

Steps to Reproduce

Make a workspace from a remote server → Open cursor app → Attempt to go to the changes tab.

Expected Behavior

The changes tab should retry when I authenticate and display all the changes.

Screenshots / Screen Recordings

Operating System

Windows 10/11

Version Information

Version: 3.0.12 (system setup)
VSCode Version: 1.105.1
Commit: a80ff7dfcaa45d7750f6e30be457261379c29b00
Date: 2026-04-04T00:13:18.452Z
Layout: glass
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.26200

Additional Information

This REALLY puts a damper on my productivity and making changes and shipping them. Cant do that if I cant see what the changes are or do commits.

Does this stop you from using Cursor

Yes - Cursor is unusable

Hey, thanks for the report. This is a known issue. Git features in the Agents Window Glass don’t work correctly when you connect over remote SSH. The team is aware, and your report helps us prioritize it.

For now, the workaround is to use the classic layout not Glass when working with a remote SSH workspace.

As a temporary option for commits, you can use the terminal directly with git status, git add, git commit.

Let me know if any of this helps.

1 Like

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

“Failed to load changes” in the changes window on the new version of the cursor IDE(v3). Only happen on a project via SSH.

Steps to Reproduce

Open a workspace via SSH
Make changes
View the changes(should display “Failed to load changes”)

Expected Behavior

Should display the proper changes affected to the codebase

Operating System

Windows 10/11

Version Information

Version: 3.0.12 (user setup)
VSCode Version: 1.105.1
Commit: a80ff7dfcaa45d7750f6e30be457261379c29b00
Date: 2026-04-04T00:13:18.452Z
Layout: glass
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.26200

Does this stop you from using Cursor

No - Cursor works, but with this issue

1 Like