File Indexing Regression: Broken Path Resolution Beyond Top-Level Directory
Status Closed — not planned
Maintainer reply None cached
Workaround ✓ Mentioned in thread ↓
Activity 13 comments · opened Aug 6, 2025 · closed Jan 9, 2026
Bug Description
In the 1.0.69 version my files are no longer being indexed properly. I can't @my-file/path anymore. It is only recognizing like top level files
Environment Info
- Platform: darwin
- Terminal: iTerm.app
- Version: 1.0.69
- Feedback ID: cd894f96-e4dc-45f5-9a16-20089792ef9a
Errors
[]
13 Comments
Found 3 possible duplicate issues:
If your issue is a duplicate, please close it and 👍 the existing issue instead.
<sub>This issue will be automatically closed as a duplicate in 3 days if there are no additional comments. To prevent auto-closure, please 👎 this comment.</sub>
🤖 Generated with Claude Code
The original behavior was that using
'@'would bring up the directory. Now, please try using'@/'as a temporary workaround.+1 this is also happening to me after update to v1.0.69. This makes claude code pretty unsusable in large repos and it's not the first time it happens.
EDIT: Confirmed downgrading to v1.0.68 fixes the issue
THANK YOU SO MUCH BRO
Getting the same https://github.com/anthropics/claude-code/issues/5291
Having the same issue
Has this been fixed or addressed at all yet? Using
@/doesn't work, and removing fuzzy file referencing makes claude code literally useless in a large repo, or IMO at all.For some reason setting the env var
USE_BUILTIN_RIPGREPto0has solved my problem.claude doctorsaid that it was using bundeled search and that it was okay, but when I ranclaude --debugand tried to search for a file, I'd get an error sayingrg error (signal=null, code=2, stderr: rg: unrecognized flag --ripgrepI've reported a similar issue, but not the same: #7781
For the issue I reported, there have been several dups but all incorrectly closed, eventually pointing back to this issue here.
Thought I'd cross-reference for transparency.
+1 on @nCubed 's comment.
This issue has been inactive for 30 days. If the issue is still occurring, please comment to let us know. Otherwise, this issue will be automatically closed in 30 days for housekeeping purposes.
This issue has been automatically closed due to 60 days of inactivity. If you're still experiencing this issue, please open a new issue with updated information.
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.