Agent View: No inline editor diffs for files in secondary workspace roots (multi-root workspace)

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

In a multi-root workspace, when the agent edits files in a secondary workspace root (not tracked by the primary repo’s git), no inline diffs appear in the editor. The changes are applied directly without any diff highlighting or Accept/Reject buttons.

The agent chat panel shows the diffs correctly (e.g., “Review +11 -9”), but the editor shows only the final state — no green/red highlighting, no “1 of N” navigation.

This worked correctly in Editor View (Cursor 2) — the same files showed full inline diffs with Accept/Keep buttons.

Steps to Reproduce

  1. Set up a multi-root workspace where a secondary root (e.g., clients/) is outside the primary git repo
  2. Switch to Agent View (Cursor 3)
  3. Ask the agent to make edits to a file in the secondary workspace root (e.g., a .md file)
  4. Observe: no inline diffs in the editor, changes are auto-applied
  5. Switch to Editor View (Cursor 2) and repeat — inline diffs appear correctly

Expected Behavior

Inline diffs with Accept/Reject buttons should appear in the editor for all agent edits, regardless of which workspace root the file is in — matching the Editor View behavior.

Operating System

MacOS

Version Information

Version: 3.0.9
VSCode Version: 1.105.1
Commit: 93e276db8a03af947eafb2d10241e2de17806c20
Date: 2026-04-03T02:06:46.446Z
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: Darwin arm64 25.2.0

For AI issues: which model did you use?

claude-4.6-opus

Additional Information

This forces me back to Editor View, until I can view diffs in files the new Agents View is unusable for me.

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

Hi Zach,

This is a known issue. Agent View (Glass) currently only tracks diffs for the first workspace root, so in a multi-root setup, changes in secondary roots won’t show inline diffs.

For now, you can use Editor View as the workaround: Cmd+Shift+P > Toggle Editor Layout to switch back. As you noticed, Editor View handles multi-root diffs correctly.

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

I made some changes via the new agent window mode in the second folder of my workspace, but when I click “review” it shows uncommited files from the first project only.

To clarify, at the same time I see correct review via “normal” chat UI in VSCode-like cursor.

Steps to Reproduce

  1. Create a workspace with several root folders. Each one has its own git repo. Make some commits to all of them.
  2. Make changes to the first (kinda main) folder, but do not commit them.
  3. Go to agent window and ask it for some changes in the second folder.

The review now reviewing the changes from the first folder and completely does not show the changes just made in the chat.

Expected Behavior

Review shows actual changes made in chat window

Operating System

MacOS

Version Information

Version: 3.0.9
VSCode Version: 1.105.1
Commit: 93e276db8a03af947eafb2d10241e2de17806c20
Date: 2026-04-03T02:06:46.446Z
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: Darwin arm64 25.3.0

For AI issues: which model did you use?

Composer 2 fast, but I think it does not matter

Does this stop you from using Cursor

Yes - Cursor is unusable

Hey, thanks for the report. This is a known issue. Agent Window Glass doesn’t support multi-root workspaces correctly right now. Review is tied to the first folder in the workspace, so changes in the second folder don’t show up.

Like you noticed, review works correctly for all folders in the normal Editor View via Cmd+Shift+P then Toggle Editor Layout. For now, that’s the main workaround.

The team is aware, and your report helps us prioritize it. Let me know if you’ve got any other questions.

Thanks Mohit - just wanted to follow up and see if there’s any timeline for this getting resolved? Would love to start using the new Agents view, but this is keeping me in the Editor view for the time being.