Recent CURSOR Update Issues – Unable to Read Files/Folders?

[kimthu91]

Hi everyone,

I’ve noticed that CURSOR has been performing worse after recent updates. Specifically:

• When I provide a file or folder, CURSOR keeps saying “Cannot read” or “File not found,” even though it handled this perfectly before.
• It seems like its ability to process source code has significantly declined.
• Some features that were previously very useful are now unstable or completely broken.

Has anyone else experienced similar issues? Is there a way to fix this or roll back to an older version? If this is a common issue, I hope the dev team addresses it soon.

Thanks!

[deanrie]

Hey, which version of Cursor are you using?

[kimthu91]

In this morning update version is cursor-0.45.14-build-250219jnihavxsz-x86_64

[kimthu91]

However, the issue has been present since the previous update, which was 2-3 days ago, though I don’t remember the exact version. It is unable to read anything and requires me to provide the exact file

[sonovice]

I am seeing the same issue in “Edit” mode:

Version: 0.46.3
VSCode Version: 1.96.2
Commit: fce3511bab261b4c986797f3e1e40e7621bbd010
Date: 2025-02-24T11:21:00.260Z
Electron: 32.2.6
Chromium: 128.0.6613.186
Node.js: 20.18.1
V8: 12.8.374.38-electron.0
OS: Darwin arm64 24.3.0

EDIT:
Interestingly it works fine if I add “Here is access to all files: @src” to the prompt instead of just @src.