Worktree not applying all file changes

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Worktree not showing or applying all active file changes.

Steps to Reproduce

Start a new agent in worktree mode.
Request some changes to be made.
Chose “Apply” to apply all file changes to main repo.
Click “Undo Apply”
Ask for further changes in the worktree.
If the next set of changes only involved changing 1 file (even though there are 3 file changes in the workspace), it will only let you Apply the file where the most recent changes were made.

Expected Behavior

In the agent chat, you should always see a list of all active file changes, not just the ones the editor has changed in the last message. You should be able to Apply/Undo all file changes from agent, not just the file changes from the most recent message.
Before 2.4 update, If I clicked “Undo Apply” and continued conversation with the agent in the worktree, I would always be able to apply all file changes at any time. This is the behavior I expect. It makes worktree agent not usable because once you apply changes the first time then undo, and request more changes, you never are then able to apply all changes again.

Operating System

Windows 10/11
MacOS

Version Information

Version: 2.4.22 (Universal)
VSCode Version: 1.105.1
Commit: 618c607a249dd7fd2ffc662c6531143833bebd40
Date: 2026-01-26T22:51:47.692Z
Build Type: Stable
Release Track: Default
Electron: 39.2.7
Chromium: 142.0.7444.235
Node.js: 22.21.1
V8: 14.2.231.21-electron.0
OS: Darwin arm64 24.6.0

Does this stop you from using Cursor

No - Cursor works, but with this issue

Worktree (Parallel Agents) Workflow
3

Hey, thanks for the report. This is a known issue with the review panel in worktree mode. After Undo Apply, it only shows changes from the agent’s last message, not all accumulated changes.

The team is aware of this bug, and your report helps us prioritize it.

Unfortunately, there’s no workaround right now. You’ll need to either avoid using Undo Apply, or apply the changes right away without going back to editing in the worktree.

Could you share the Request ID from the chat where this happens? (Chat context menu → Copy Request ID). This will help the engineers add more context to the bug. Let me know if anything changes in the next versions.