[BUG] File autocomplete just stopped working (using @[Filename])
Resolved 💬 26 comments Opened May 28, 2025 by smaccoun Closed Aug 22, 2025
💡 Likely answer: A maintainer (ant-kurt, collaborator)
responded on this thread — see the highlighted reply below.
Environment
- Platform (select one):
- [ X] Anthropic API
- [ ] AWS Bedrock
- [ ] Google Vertex AI
- [ ] Other: <!-- specify -->
- Claude CLI version: 1.0.5 (Claude Code)
- Operating System: macOS 15.4.1
- Terminal: iTerm2
Bug Description
Not sure what happened but suddenly every time i try to use the @ symbol to start autocompleting a file, nothing actually happens. It doesn't sort or find any files. I don't think I changed anything with my claude configs, just upgraded
Steps to Reproduce
- Open claude code in iTerm2
- Start typing: "This is a file @Somefile"
- Observe using the @ symbol no longer autocomplete
Expected Behavior
It should start autocompleting
Actual Behavior
It doesn't :(
Additional Context
I dont think anything changed via configs (I certainly didn't change anything), but I'll look for this
26 Comments
+1
Same issue! Also, it only happens on one repository, other repos I have show file suggestions as expected.
That's a really interesting point @quezadaesteban I just discovered the same thing. The
@autocomplete works in any other repo (I just tested a bunch of random ones), but in the giant production monorepo I've been working out of a while it just completely stopped yesterday. So at least its not a system issue....I'm also having the same issue after updating when using Claude Code in a large monorepo. Downgrading to 1.04 fixes the issue for me. M4 MacOS Sequoia.
Can confirm fix for now is just to downgrade
I had the same autocomplete issue in a largish monorepo, but hit the bug described in #1392 after downgrading to 1.0.4. Downgrading to 1.0.3 fixed both things for me
Same here (Not sure if it matters but I also migrated to the local install)
Note, the issue seems to resolve itself with a fresh clone of the repository. Not sure what the cause of the initial issue, but hopefully this can shed some light onto it.
Same, after upgrade to 1.0.5 autocomplete doesn't work, config is not respected, etc
My issue was described in #1444 and autocomplete started working for me once I removed a broken symlink which I found by running
rg --files --follow . >/dev/null---
I had claude code beautify then compare cli.js from the claude code node module. It seems to think the problem was caused because claude started listing files with
rg --files --follow, instead ofrg --files, but that command returns exit code 2 if it encounters any broken symlinks and claude isn't properly handling that exit code so it just failed silentlyThank you @joshcurtis that totally worked for me!
Thank you @joshcurtis. Your description helped me solve a closely related issue: I had a sub-folder (attached to a Docker container) that my user, and hence Claude Code, did not have read access to. The
rg --files --follow . >/dev/nullcommand reported aPermission deniederror for that folder, but unfortunately I cannot remove that folder. However, I found a solution by writing the folder's path to an.ignorefile in the top-most folder, which thergtool reads and adheres to.it helpd, thank you bro!
I have the same problem but
rgreports no broken symlinks or other errorsHmm, I might actually be having a different issue if you guys aren't seeing any files at all. Mine seems to be more of a matching issue. For instance, I want to search for
EmailRequestBuilderbut only theEmatches the file:<img width="682" alt="Image" src="https://github.com/user-attachments/assets/23545923-96ee-4ff3-941f-76482fecf71f" />
If I typed
Emit loses the file:<img width="674" alt="Image" src="https://github.com/user-attachments/assets/ba2b1330-38e3-4dbc-b4e2-da91fc724efa" />
I might open a different issue if this doesn't appear to be related.
@mcantrell that is a differnt issue and one i started seeing around version
1.0.19or1.0.20or so. Not sure tbh but i had to downgrade again to 1.0.18 and it went away and searches all files againOK, I'll sniff around and see if there's already an open issue or add a new one.
Can confirm, downgrading to
1.0.18solves the problem for me (macos, also had no broken symlink).Same for me - downgrading to 1.0.18 solved it (MacOS, no broken symlinks)
Same for me - downgrading to 1.0.18 solved it (Ubuntu 24.04)
After analyzing the issue using Claude Code itself, it seems there is some hard limit / timeout for number of files ripgrep can process (it says 10000).
Adding more files to .rgignore resolves the issue for me (
rg --files --follow . | wc -l= ~15000 files in my case).Thanks @EgorDuplensky ! That was it for me!
Set up
.rgignoreto exclude node_modules/:Now rg is finding way less files and my auto-complete is working again!
Following the suggestion about broken symlinks, I found and fixed the problem.
find . -type l -exec test ! -e {} \; -printFor others experiencing this issue: Check for broken symlinks using the find command above. Circular symlinks seem to break the file indexing for me.
Thanks to the earlier suggestions in this thread! 🎯
This is still not working for me - it works on some folders but not consistently [no symlinks and sub 1000 files]
Is this dependant on container configurations?
This should be working better now:
claude /doctorwhich can help show if ripgrep is available/mntdirectories + improve recovery on partial searchesThis 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.