[BUG] Incoherent path completion options produced by '@'
Status Open
Reported on v2.1.220
Maintainer reply None cached
Activity 0 comments · opened Aug 23, 2026
Preflight Checklist
- [x] I have searched existing issues and this hasn't been reported yet
- [x] This is a single bug report (please file separate reports for different bugs)
- [x] I am using the latest version of Claude Code
What's Wrong?
Regarding the paths that appear as selectable options when using the '@' notation: broken in two ways.
- The filtered-as-type behavior often surfaces paths that do not match what is typed while ignoring files that do exist which do match what is typed. Typing the absolute path does not help. In such cases, if I press TAB after typing the exact absolute path, auto-complete replaces it with a random file's path that that does not match what I have typed and sometimes will be outside the project/directory I am working in (almost like it is selecting from some kind of pre-determined global cache).
- Even when the correct files are listed, the harness lists them out of order. For example, I have a directory containing timestamp-prefixed filenames, but even they are listed in seemingly random order.
What Should Happen?
The same thing that happens natively in any of the three supported shells (bash, zsh, powershell): tab completion obeys what is typed because surfacing anything else is the opposite of useful here. The files that are surfaced are not shuffled into random order, they keep their normal alpha-numerical ordering (as they would natively in the shell).
Error Messages/Logs
Steps to Reproduce
- Press and hold the Left SHIFT key or the Right SHIFT key.
- While holding the Left SHIFT key or the Right SHIFT key, press the '2' key (should result in an '@' character appearing).
- Start typing a relative path.
- Observe.
- Repeat steps 3 and 4 with an absolute path.
- Try TAB completion during steps 3-5.
- Try steps 3-6 with a file that is within a subdirectory that existed at the start of the session.
- Try steps 3-6 with a file that did not exist that is within a directory that did not exist at the start of the session but does now.
Claude Model
_No response_
Is this a regression?
I don't know
Last Working Version
_No response_
Claude Code Version
2.1.220
Platform
Other
Operating System
Ubuntu/Debian Linux
Terminal/Shell
Xterm
Additional Information
_No response_