Diffs are shown as all new files for some agent calls (worktree)

[KjetilH (Kjetil Hårtveit)]

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

All diffs are shown as new files for some agent calls (worktree). When it happens it’s practically impossible to review the generated code via the review feature.

When it occurs it seems the path to the files are prefixed by “/workspace” (screenshot 1), this does not happen in other cases when the diffs are normal (screenshot 2).

Btw, I tried to upload 3 screenshots but can only upload 1.

Steps to Reproduce

I’m not sure what causes it, and it’s not down to individual models. It has happened with Sonnet 4.5 (screenshot 1) and GPT-5 Codex High (screenshot 3) for me.

Expected Behavior

We should be able to diff only changes

Screenshots / Screen Recordings

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.0.69 (user setup)
VSCode Version: 1.99.3
Commit: 63fcac100bd5d5749f2a98aa47d65f6eca61db30
Date: 2025-11-07T18:21:29.650Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Windows_NT x64 10.0.26100

For AI issues: which model did you use?

Composer 1, Sonnet 4.5, gpt-5-codex-high

For AI issues: add Request ID with privacy disabled

Request ID for buggy diff (gpt-5-codex-high): bc-bdb0cd44-65c5-43e6-8966-9c35a9183ae2
Request ID for working diff (Composer 1): bc-23b5ba96-ee1e-453f-aaf6-5b93363d89c4

Does this stop you from using Cursor

No - Cursor works, but with this issue

[deanrie]

Hey, thanks for the report. This looks like a worktree path handling issue: the “/workspace” prefix makes the diff system treat modified files as entirely new.

I’ll escalate this to the team. If you notice any additional patterns about when it occurs vs. when it works (beyond the models you mentioned), please share - it’ll help narrow down the cause.