Every file in repo has cursorignore icon

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Every single file in my repo has the file indicating it is ignored in .cursorignore. When I hover the icon it says “AI features disabled (file in .cursorignore)”.

There is no .cursorignore file in my repo.

Steps to Reproduce

I am uncertain how to reproduce this issue. It only appears in one repo. I stopped working on it last night and this issue did not occur. When I began work this morning it appeared.

Expected Behavior

Only files listed in .cursorignore or global ignore list should be ignored.

Screenshots / Screen Recordings

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.6.6 (Universal)
VSCode Version: 1.99.3
Commit: 9455eaa4c87f2bad91eda3f2bc9b42b16eae1080
Date: 2025-09-11T01:16:54.096Z
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Darwin arm64 24.5.0

Additional Information

My cursor global ignore list is:

**/.env
**/.env.*
**/credentials.json
**/credentials*.json
**/secret.json
**/secrets.json
**/*.key
**/*.pem
**/*.pfx
**/*.p12
**/*.crt
**/*.cer
**/id_dsa
**/.ssh/id_*

Does this stop you from using Cursor

No - Cursor works, but with this issue

Hey, thanks for the report. It’s really strange. Could you try creating a .cursorignore file? It might solve the problem. Also, let me know if the same issue occurs in other projects, so we can determine if it’s a global issue or not.

Creating or modifying a .cursorignore file doesn’t appear to have any effect. And yeah this only appears in one repo, the other main repo I’m in at work day to day never has this issue.

It’s very strange. The only way I’ve been able to fix it is to repeatedly run developer: reload window a bunch of times. It takes a few reloads, but it eventually goes away. I can’t trigger the issue so hard to reproduce to narrow it down further, but I’ll try more methodically testing it next time it comes up.

It would be great if you could reproduce this, thanks.

I am having the same issue

Ok I believe I can reproduce this — it appears to only occur when my computer is restarted. running developer: reload window repeatedly appears to fix it eventually, but it takes an inconsistent number of reloads to clear the warnings. @deanrie are there specific logs you’d like me to share?

Hello, I have the same issue @deanrie. I used cmhac’s advice to reload the window and it worked.

1 Like

I just had this happen to me as well. Mine happened on an Ansible project I am working on and after a reboot to upgrade MacOS. I was able to resolve in the same manner.

Version: 1.6.45 (Universal)

VSCode Version: 1.99.3

Commit: 3ccce8f55d8cca49f6d28b491a844c699b8719a0

Date: 2025-09-22T18:22:38.013Z (17 hrs ago)

Electron: 34.5.8

Chromium: 132.0.6834.210

Node.js: 20.19.1

V8: 13.2.152.41-electron.0

OS: Darwin arm64 24.6.0

Same issue. Reloading the window isn’t working. Only happening in one repo

Version: 1.6.45
VSCode Version: 1.99.3
Commit: 3ccce8f55d8cca49f6d28b491a844c699b8719a0
Date: 2025-09-22T18:22:38.013Z
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Darwin arm64 25.0.0

Happening to me too, for every file regardless of directory.

Version: 1.6.45 (user setup)
VSCode Version: 1.99.3
Commit: 3ccce8f55d8cca49f6d28b491a844c699b8719a0
Date: 2025-09-22T18:22:38.013Z
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Windows_NT x64 10.0.26100

Happened to me too but just closing and reopening the window a few times solved it.

Version: 1.6.35 (system setup)
VSCode Version: 1.99.3
Commit: b753cece5c67c47cb5637199a5a5de2b7100c180
Date: 2025-09-19T17:39:38.846Z
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Windows_NT x64 10.0.26100

Having same issue, what is solution? I have git worktrees

Version: 1.6.45 (Universal)
VSCode Version: 1.99.3
Commit: 3ccce8f55d8cca49f6d28b491a844c699b8719a0
Date: 2025-09-22T18:22:38.013Z
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Darwin arm64 24.6.0

Hey, try this:

This issue was fixed in version 1.7, which will be available soon.

This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.