Missing File Discovery with "@" After Migration and Update

Found 3 possible duplicate issues:

1. https://github.com/anthropics/claude-code/issues/4826
2. https://github.com/anthropics/claude-code/issues/4933
3. https://github.com/anthropics/claude-code/issues/1397

If your issue is a duplicate, please close it and 👍 the existing issue instead.

🤖 Generated with Claude Code

Same here

same here. the whole experience is broken. you can't select the files and also it seems cc doesn't respect .gitignore now.

edit:
i also observed that the autocomplete of @ now doesn't ignore case so for example, if you type profile and you have a file called Profile, it doesn't show up.

same here, it seems CC there is a sort of filter that filter out the search result for the mention, only some files and folders are listed

same here Version 1.0.69. This needs to be fixed ASAP because it severely undermines Claude Code usability.

The original behavior was that using '@' would bring up the directory. Now, please try using '@/' as a temporary workaround.

The original behavior was that using '@' would bring up the directory. Now, please try using '@/' as a temporary workaround.

this works (although still a bit slow). Thank you so much!

Getting the same https://github.com/anthropics/claude-code/issues/5291

They fix in 1.0.70

They fix in 1.0.70

Nope, still not fixed. Same issues as described above. I do @ and I can see some of my files and dirs in the root of my project but not all and most importantly, my src dir does not show up and nothing inside of it is "searchable". This makes file referencing unusable and really is destructive to the CC experience.

See here for more details on my situation: https://github.com/anthropics/claude-code/issues/5284#issuecomment-3175210652

Now, please try using '@/' as a temporary workaround.

I have seen this advice in a few different related gh issues but this does not work for me. Nothing shows up if I start with @/. I am using CC in WSL on Windows.

Ok I figured it out! I documented the solution here: https://github.com/anthropics/claude-code/issues/4741#issuecomment-3177976916

I do not want to re-spam / copy the entire solution / details in several gh issues so I am linking back to my detailed solution and write-up. Hope this helps others!!

Unfortunately, that didn't fix it for me. I also don't have a ripgrep config file

Unfortunately, that didn't fix it for me. I also don't have a ripgrep config file

Do you have ripgrep installed for sure? See: https://github.com/anthropics/claude-code/issues/4741#issuecomment-3178151886

It's installed yes, I just checked.

The thing is, Claude is actually able to see and find all these files, I've verified that by asking it to try. But the completions with the "@"-syntax don't work properly.

Maybe it has something to do with the installation of claude code, which is somehow broken for me. Whenever I try to update claude, I get an error:

npm install -g @anthropic-ai/claude-code

npm error code ENOTEMPTY
npm error syscall rename
npm error path /opt/homebrew/lib/node_modules/@anthropic-ai/claude-code
npm error dest /opt/homebrew/lib/node_modules/@anthropic-ai/.claude-code-2DTsDk1V
npm error errno -66
npm error ENOTEMPTY: directory not empty, rename '/opt/homebrew/lib/node_modules/@anthropic-ai/claude-code' -> '/opt/homebrew/lib/node_modules/@anthropic-ai/.claude-code-2DTsDk1V'
npm error A complete log of this run can be found in: /Users/swiftedmind/.npm/_logs/2025-08-12T11_19_15_037Z-debug-0.log

Not even npm uninstall works, I have to manually remove everything and re-install. Not sure if this might be related?

Edit: Okay, I fixed the installation (see https://github.com/anthropics/claude-code/issues/1025#issuecomment-3136367489)

But the autocompletion is still broken

We shipped some changes for this recently. Next steps:

• claude /doctor should tell you if Search (which includes @ file mentions and custom agents / slash commands) is working
• If not, see https://docs.anthropic.com/en/docs/claude-code/troubleshooting#search-and-discovery-issues

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.