Agent Review fails to open files with issue when working in a nested workspace

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

When the workspace is a subdirectory of a monorepo (not the repo root), the review agent finds issues but cannot open or fix them because it uses file paths relative to the repository root instead of the workspace root. The UI shows “nothing to review” when reviewing an issue, and fix attempts report “Related files (could not be opened)” for the same reason.

Environment

  • Workspace: A folder that is a subdirectory of a git repository (e.g. my-monorepo/apps/frontend).

  • Repo root: The repository root (e.g. my-monorepo).

  • Expected: Paths and file opening use the workspace root (the folder the user opened).

  • Actual: Paths are relative to the repo root, so they don’t resolve inside the workspace and files cannot be opened

Steps to reproduce

  1. Open only a subdirectory of a monorepo as the Cursor workspace (e.g. my-monorepo/apps/some-app), not the full repo root.

  2. Run the review agent (e.g. on the current branch or PR).

  3. Wait for the agent to finish; it reports that it found issues.

  4. Try to review one of the reported issues (e.g. click to view or apply feedback).

  5. Observed: The UI shows “nothing to review” (or equivalent).

  6. Ask Cursor to fix one of the reported issues.

  7. Observed: At the end of the fix attempt, a message like:

  • “Related files (could not be opened): path/to/file/from/repo/root (lines 101-102)”

  • The path is from the repository root, not from the workspace, so Cursor cannot open it in the current workspace.

Expected behavior

  • Paths in review results and fix flows are relative to the workspace root (or otherwise resolvable in the opened folder).

  • The user can open the related files and review and apply fixes for the issues the agent found.

Actual behavior

  • Paths are given from the repository root.

  • Because the workspace is a subdirectory, those paths do not resolve in the current workspace.

  • Review: Shows “nothing to review” when trying to review an issue.

  • Fix: Shows “Related files (could not be opened): (lines X–Y)” and the fix cannot be applied.

Screenshots / Screen Recordings

Screenshot 2026-02-18 at 8.26.54 PM.png
Screenshot 2026-02-18 at 8.26.54 PM.png1696×514 14.6 KB

Operating System

MacOS

Version Information

Version: 2.5.17
VSCode Version: 1.105.1
Commit: 7b98dcb824ea96c9c62362a5e80dbf0d1aae4770
Date: 2026-02-17T05:58:33.110Z
Build Type: Stable
Release Track: Default
Electron: 39.3.0
Chromium: 142.0.7444.265
Node.js: 22.21.1
V8: 14.2.231.22-electron.0
OS: Darwin arm64 24.6.0

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

3

Hey, thanks for the detailed report.

This is a known issue. Agent Review resolves file paths relative to the git repo root, not the workspace root. So when you open a monorepo subfolder as your workspace, the paths don’t match and the files can’t be opened.

The team is aware. Your report helps raise visibility, especially since this directly affects monorepo workflows.

For now, the only workaround is to open the repo root as the workspace instead of a subfolder. Not ideal for large monorepos, but it will let Agent Review resolve paths correctly.

I’ll flag your report to help bump the priority.