Please undo 2.2.14

[Rakly3]

Describe the Bug

Everything is broken

Steps to Reproduce

update to 2.2.14

Expected Behavior

Things to work

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.2.14 (user setup)
VSCode Version: 1.105.1
Commit: 1685afce45886aa5579025ac7e077fc3d4369c50
Date: 2025-12-11T01:12:35.790Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Windows_NT x64 10.0.19045

Additional Information

There’s just so much things broken I don’t even know where to begin.

The worst probably are

• I can no longer apply any changes to the code
• commits don’t work
• the layout management is unintuitive. (I haven’t figured out how to get my default layout back)
• To add a new chat I have to toggle on ‘Agents side bar’, click ’
  New Agent’, and toggle the Agent Sidebar off again.
• The agent chat now has a max width making it just waste space on large screens/high resolution
• GitLens doesn’t work any more

Does this stop you from using Cursor

Yes - Cursor is unusable

[Rakly3]

Maybe this has something to do with it.

I asked the agent which files it keeps getting blocked for and it pretty much told me it can’t access files that are not supposed to be blocked.

Request ID: 4f19dab5-b83d-4aee-a960-dbebdb004bf3

Files blocked by .cursorignore:

None of the source files match the patterns in .cursorignore. The patterns block:

• Python cache files (_pycache_/, *.pyc, etc.)

• Virtual environments (venv/, env/, etc.)

• Test artifacts (.pytest_cache/, .coverage, etc.)

• IDE files (.vscode/*, .idea/, etc.)

• Log files (*.log, logs/)

• Temporary files (*.tmp, tmp/, temp/)

• Data files (*.pkl, *.h5, *.hdf5)

• Project-specific generated files (high_score.txt, *.save, *.bak)

However, when I try to read certain files, I get “Read blocked by cursor ignore” even though they don’t match these patterns:

Files that are blocked:

• requirements.txt

• src/agents/dqn_agent.py

• src/utils/logger.py

• src/utils/config.py

• src/models/base.py

• src/models/ppo.py

• src/models/dqn.py

• src/models/dynamics_model.py

• src/trainer.py

• src/gui/renderer.py

• .gitignore

Files I can read:

• src/agents/ppo_agent.py (read successfully)

• .cursorignore (read successfully)

This suggests Cursor may be using additional ignore rules beyond .cursorignore, or there’s a configuration issue. The files exist and are readable via terminal commands, so they aren’t actually ignored by the patterns shown.

Should I check for other ignore configuration files or investigate why these specific files are blocked?

[Rakly3]

Summary

The .cursorignore file is not blocking these files. None of the patterns in .cursorignore match the blocked files.

Findings

1. .cursorignore patterns are correct — they only block:

• Cache files (_pycache_/, *.pyc)

• Virtual environments

• Test artifacts

• Log files

• Temporary files

• Data files (*.pkl, *.h5)

1. Pattern of what I can read:

• src/agents/ppo_agent.py — currently open in your IDE

• src/main.py — recently viewed

• src/config/config.yaml — recently viewed

• .cursorignore — currently open

• src/agents/dqn_agent.py — not recently viewed

• src/utils/logger.py — not recently viewed

• requirements.txt — not recently viewed

• README.md — not recently viewed

1. Files exist and are readable via terminal — they’re not actually ignored.

Conclusion

Cursor appears to restrict file access via read_file to files that are:

• Currently open in the editor

• Recently viewed in the IDE

• Or part of the active editor context

This is separate from .cursorignore. The files aren’t ignored; they’re just not accessible through the read_file tool unless they’re in the editor’s active context.

Solution

To access these files:

1. Open them in your IDE (they’ll become readable)

2. Use terminal commands (which I did to read their contents)

3. Or ask me to use terminal commands to read specific files

The .cursorignore file is working as expected and is not the cause of the blocking.

[Rakly3]

how about writable? You tried to create a new markdown file but couldn't

Write blocking analysis

Findings:

1. No .cursorignore patterns match the files I tried to create:

• LIBRARY_REPLACEMENT_ANALYSIS.md — no match

• test_write.txt — no match

• test_write.md — no match

1. Git doesn’t ignore these files.

2. Terminal commands can create files successfully.

3. The error message says “Read blocked by cursor ignore” even for write operations, which is misleading.

Conclusion

Cursor appears to block writes through the write tool, even when:

• The file doesn’t match any .cursorignore patterns

• The file would be allowed by git

• Terminal commands can create the same files

This suggests:

1. Cursor applies .cursorignore to both reads and writes.

2. There may be additional write restrictions beyond .cursorignore.

3. The error message may be misleading (it says “Read blocked” for writes).

Possible solutions

1. Add an exception to .cursorignore for documentation files:

   # Allow documentation files

   !*.md

   !docs/

2. Use terminal commands to create files when needed.

3. Check if there’s a Cursor workspace setting that restricts file creation.

Should I add exceptions to .cursorignore to allow markdown documentation files, or investigate further?

It’s not just document files, I just happen to have asked about a markdown file.

[leoing]

2.2.17 on Mac broke my history, and did incomplete edits etc.

Going back to 2.1.50

[deanrie]

Hey, thanks for the report. This looks like a set of regressions in 2.2.x.

What to check and temporary workarounds:

• Read/write blocked:
  • Settings > General: check Global Cursor Ignore List and Hierarchical Cursor Ignore
• Check .cursorignore in parent folders of the project
• Temporary workaround: open the needed files in the editor - reads should work; use the terminal for creating/modifying files
• Fully restart Cursor and temporarily disable MCP servers in the project
• Revert changes not working:
  • Temporary workaround: use CMD+Z or the file Timeline (Right click > Open T imeline)
• GitLens and partial edits:
  • Open Extension Monitor and temporarily disable GitLens, then test
  • Run a test with cursor --disable-extensions

Please help with diagnostics:

• A short video or screenshots for each symptom separately
• Exact repro steps
• System info: Help > About
• Console: Help > Toggle Developer Tools > Console - copy errors
• Request IDs for read/write failures and unapplied edits
• List of installed extensions and GitLens version

Let me know if any of the above helps and share the requested data.

[NikolaiKulikov]

I’m on Cursor 2.2.20. GitLens isn’t showing git graph in Panel. It shows the graph if you switch to “Prefer Commit Graph in Editor” though.

In Output for the extension:

(gitlens.graph) Failed to show panel (f8f5f1c1-6ab6-4136-84df-e710c60cb064)

Error: Webview is disposed

I’m on GitLens 17.7.1 The same version works on VS Code 1.107.0 just fine.

[Rakly3]

this has all the tests done by the agent (There’s more than what I posted in this thread)

Request ID: 4f19dab5-b83d-4aee-a960-dbebdb004bf3

I’m not sure what to take screenshots of that shows how something didn’t happen.

̶I̶ ̶a̶l̶s̶o̶ ̶r̶e̶v̶e̶r̶t̶e̶d̶ ̶t̶o̶ ̶2̶.̶0̶.̶7̶7̶ ̶f̶o̶r̶ ̶t̶h̶e̶ ̶t̶i̶m̶e̶ ̶b̶e̶i̶n̶g̶ ̶w̶h̶e̶r̶e̶ ̶e̶v̶e̶r̶y̶t̶h̶i̶n̶g̶ ̶i̶s̶ ̶s̶t̶i̶l̶l̶ ̶w̶o̶r̶k̶i̶n̶g̶ ̶f̶o̶r̶ ̶m̶e̶.̶

---

̶E̶d̶i̶t̶:̶ ̶A̶c̶t̶u̶a̶l̶l̶y̶,̶ ̶I̶ ̶a̶p̶p̶l̶i̶e̶d̶ ̶a̶n̶ ̶u̶p̶d̶a̶t̶e̶ ̶a̶g̶a̶i̶n̶ ̶a̶n̶d̶ ̶n̶o̶w̶ ̶i̶t̶’̶s̶ ̶2̶.̶2̶.̶2̶0̶.̶ ̶S̶o̶ ̶f̶a̶r̶ ̶t̶h̶i̶n̶g̶s̶ ̶s̶e̶e̶m̶ ̶t̶o̶ ̶b̶e̶ ̶b̶a̶c̶k̶ ̶t̶o̶ ̶n̶o̶r̶m̶a̶l̶,̶ ̶e̶v̶e̶n̶ ̶G̶i̶t̶L̶e̶n̶s̶

Version: 2.2.20 (system setup)
VSCode Version: 1.105.1
Commit: b3573281c4775bfc6bba466bf6563d3d498d1070
Date: 2025-12-12T06:29:26.017Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Windows_NT x64 10.0.19045

---

---

Edit 2:

• I spoke too soon. The Agent I still had open from before the update is still able to work normally.
• A new agent has the issues still as described originally. (2.2.20)
  dcbb8938-147f-4cc5-b884-24a042125a3f

[deanrie]

Thanks for the additional info. A very important detail is that old Agents (opened before the update) work fine, while new ones have trouble accessing files.

This looks like a regression in initializing new chats in 2.2.x. To help the dev team:

Critical data for investigation:

1. Help → Toggle Developer Tools → Console - copy all errors (especially when creating a new Agent)
2. Check Settings → General:
   • Global Cursor Ignore List (is it empty?)
   • Hierarchical Cursor Ignore (enabled/disabled?)
3. The list of installed extensions (especially the GitLens version)
4. Exact steps to reproduce the write lock (which file, what command to the Agent)

I’ll pass this information to the team as well.

[abcde090 (Dan Wang)]

I am facing the same issue. Gitlens isn’t showing git graph in Panel. It works in Editor mode.

[NikolaiKulikov]

I’m on 2.2.43 , I don’t have this problem with GitLens anymore

[Rakly3]

I gave trying an update another go, and Gitlens issue was fixed, but still had the same issue of agents not being able to read or write any files. Keeps saying blocked by .corsorignore even if i delete the file, restart etc.

[Rakly3]

1. Why is this marked as resolved? The Gitlens thing was just ONE of the symptoms, not the actual issue.

2. Having to use an older version isn’t a fix.

3. After rolling back yesterday, today I am being pushed constantly to upgrade to the latest version. I though, ok maybe there is a big update now? I’ll give it another shot.
   Sure enough, after the update, again still the same issue, agents can’t read or edit any files any more. “blocked by .cursorignore” (which they are not.)

   It seems to me, every time I upgrade to a version with this…

   

   … the issue starts.
   Only agents/chats that were open before updating, still work; Any new ones don’t. So I also can’t start new projects.

[Rakly3]

I used an uninstaller tool to completely clean out all traces of Cursor, including windows registries, reinstalled the latest user version of Cursor. Now everything seems to work normally.

So my advice would be to do a more thorough job getting rid of certain traces when performing updates on user systems. Or do a version migration with updates.

[B_J]

i just installed the latest cursor and i cant even open the app now, and i cant open new chats

[Rakly3]

OMFG are you kidding me? It’s back!

5b8da24a-0616-4611-b6d0-b7cf8bce6baa

I just checked out Windsurf. It’s still the way Cursor used to be, and why I liked Cursor.
Even this simple thing is gone in Cursor and put in an inconvenient location:

---

I’m starting to get a bit ticked off how Cursor keeps making the UX worse with every update with stuff no one asked for.

---

I’m not going to pretend my $200 is going to impact your overall business, but I am seriously starting to consider other options.