Find All References fails on small C# files with “Documents above the size limit cannot be synchronized with extensions” until the file is pre-opened (Windows, single-root, not WSL)

Support Bug Reports
, ,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Summary

On a local Windows single-root Unity C# workspace (not WSL, not multi-root), Find All References cannot open a referenced .cs file that has not been opened in the current session.

The toast / error is:

Steps to Reproduce

The target file is ~16 KB / ~385 lines, far below the 50 MB sync limit. The file:/// URI uses a percent-encoded Windows drive letter (e%3A = E:).

This looks like the same class of bug as:

Those reports were WSL / macOS multi-root / Linux. This repro is local Windows + single-root folder + C# Find All References.

Environment

  • OS: Windows 10 (10.0.19045), local disk, no WSL / SSH / Remote
  • Workspace: single-root folder (E:\unityP\ET2\20260706), Unity C# project
  • Cursor: 3.16.24 (stable)
  • VS Code version: 1.128.0
  • Commit: 1da364a6e1b9a7f7caabc58cecc5766c173673b0
  • Language: C# (Unity). Triggered from the editor context menu 查找所有引用 / Find All References (Shift+Alt+F12)

Please treat the version numbers as “from Help → About on this machine”; I can paste a screenshot if needed.

Repro steps

  1. Fully quit Cursor and reopen it.
  2. Open the single-root Unity project.
  3. Open Assets/src/HotelGame/HotelWallet.cs.
  4. Do not open Assets/src/HotelGame/TriageReceptionistHirePoint.cs.
  5. Place the cursor on a referenced symbol (e.g. TrySpendCost / GetBalance / AddPendingSpend) and run Find All References.
  6. Click a result that points to TriageReceptionistHirePoint.cs (or wait for the extension to open that file).

Expected

The small .cs file opens and the reference location is shown.

Actual

Cursor refuses to open the file with:cannot open file:///e%3A/…/TriageReceptionistHirePoint.cs. Detail: Documents above the size limit cannot be synchronized with extensions.

Operating System

Windows 10/11

Version Information

Version: 3.16.24 (user setup)
VS Code Extension API: 1.128.0
Commit: 1da364a6e1b9a7f7caabc58cecc5766c173673b0
Date: 2026-08-15T21:42:10.610Z
Layout: IDE
Build Type: Stable
Release Track: Default
Electron: 40.10.3
Chromium: 144.0.7559.236
Node.js: 24.15.0
V8: 14.4.258.32-electron.0
xterm.js: 6.1.0-beta.291
OS: Windows_NT x64 10.0.19045

Does this stop you from using Cursor

No - Cursor works, but with this issue

7

Hey @txfic, This is the same issue we’re already tracking, and despite the wording it isn’t about file size.

Quickest unblock: open the target file once via Ctrl+P (or the file tree) before running Find All References. It also helps to keep or undo any pending agent changes on that file, then fully quit and reopen.

To help us pin the trigger: open Assets/src/HotelGame/TriageReceptionistHirePoint.cs directly and check whether it has pending agent changes (inline or in the Review Changes view). Letting us know either way narrows it down.

No timeline yet, but I’ll post here when there’s an update. One heads-up so you don’t chase it: updating to the latest version won’t fix this on its own yet.

8

There are no pending agent changes. I use auto-accept for changes. These files have been modified by the agent before, but they may not have been touched for 1–2 days before the issue appeared. This usually happens after Cursor is restarted.

Mohit <[email protected]> 于2026年9月18日周五 16:20写道：

9

Thanks @txfic, that’s useful. It’s not about changes waiting for review, it’s tied to files the agent edited in an earlier session (even auto-accepted, days-old), which is why it hits after a restart on files you haven’t opened yet. Reliable workaround until the fix ships: open the target file once via Ctrl+P before running Find All References. Updating alone won’t fix it yet, and I’ll post here when there’s an update.

12

Hey @txfic,

Quick update as promised: a fix for Find All References failing to open small files with the “Documents above the size limit” error has landed and will be included in an upcoming version of Cursor (3.23)

It covers the case you described, files the agent edited in an earlier session that you haven’t opened yet after a restart.

Until it reaches your build, opening the file once via Ctrl+P before running Find All References still works. After your next couple of updates, give it a try without pre-opening the file and let me know if you still hit it.