`@`-file autocomplete broken after v1.0.64
Status Fixed / completed
Maintainer reply ✓ Yes — ant-kurt
Workaround ✓ Mentioned in thread ↓
Activity 6 comments · opened Jul 31, 2025 · closed Aug 22, 2025
💡 Likely answer: A maintainer (ant-kurt, collaborator)
responded on this thread — see the highlighted reply below.
Environment
- Platform: Claude Code
- Claude CLI version: 1.0.64
- Operating System: macOS Sequoia 15.5
- Terminal: Terminal App
---
Bug Description
After upgrading from Claude Code v1.0.63 to v1.0.64, the @-file autocomplete feature no longer triggers. Previously, typing @ in the editor would pop up a file-path suggestion list; this behavior has stopped working entirely.
---
Steps to Reproduce
- Install or upgrade to Claude Code CLI version ≥ 1.0.64.
- Open a project in the Claude Code editor on macOS Sequoia 15.5.
- In any source file, type the
@character. - Observe that no file autocomplete suggestions appear.
---
Expected Behavior
Typing @ should trigger the file-path autocomplete dropdown, allowing selection of files within the project.
---
Actual Behavior
No autocomplete dropdown appears after typing @. Other completion features (e.g., symbol or keyword suggestions) continue to work as expected.
---
Additional Context
- Reverting to v1.0.63 restores
@-file autocomplete functionality.
Please let me know if any additional logs or configuration details would help troubleshoot this regression.
6 Comments
Found 3 possible duplicate issues:
If your issue is a duplicate, please close it and 👍 the existing issue instead.
🤖 Generated with Claude Code
Release management and quality assurance is completely non-existent at Anthropic. It's like they let AI implement features without vetting the implementation or verifying acceptance criteria. This is just one of many very sloppy releases that introduce regressions that even a rock wouldn't miss if it were QA. Sloppy release notes that are delayed days behind new versions published to npm registry as well.
How do you guys expect to stay ahead in this volatile, competitive market, when you're upsetting customers with service reliability issues and tooling quality issues?
The original behavior was that using '@' would bring up the directory. Now, please try using '@/' as a temporary workaround.
Having this same issue for about a week now. When I use @ it I can see the root directories and files (not all of them) but that's it. When I type out anything after the @ the suggestions go away. I noticed if I type out the full path, it will reference it in the thinking output.
We shipped some changes for this recently. Next steps:
claude /doctorshould tell you if Search (which includes @ file mentions and custom agents / slash commands) is workingThis 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.