[BUG] @-file browser is so buggy it needs to be disable-able

Environment

• Platform (select one):
• [x] Anthropic API
• [ ] AWS Bedrock
• [ ] Google Vertex AI
• [ ] Other: <!-- specify -->
• Claude CLI version:1.0.69
• Operating System: Ubuntu 24.04.3
• Terminal: gnome terminal on x11

Bug Description

There are several showstopping bugs in the @ file browser:

1. For larger repositories, if you type the first unique letters of the file, sometimes it finds the file, sometimes it doesn't.
2. If it _does_find it, and you immediately "accept" the path from the pull-down with enter, your path is replaced by something random. If, instead, you tap down cursor and up cursor and _then_ hit enter, everything works.
3. If the file in question doesn't have a unique set of letters (say "mod.rs"), the file browser refuses to filter down based on parent directory or other substring matching. VS code does this quite well, btw, and that code is open source (and typescript), so you could yoink it straight from there.
4. It'd be great if you could navigate the tree with tab-completion, so @src/ + tab would then show only children of src, and then type a letter to refine + tab, and so-on.
5. If I have a multi-line prompt (which are most of my prompts!), tapping the up or down key is suddenly captured by the file picker dropdown if there happens to be any @-paths that my cursor touches. Just trying to move my cursor can result in my message changing.

So -- I really appreciate the thought of @ paths -- but I'd really rather have nothing than have these issues.

Can we please add a config item that disables @ path handling altogether, so if anyone (like me) finds this irritating, they have an easy remediation?

Thanks for Claude Code!

EDIT AUG 12: There's a simple workaround -- if you avoid the @ prefix (and/or delete the @ prefix from file paths), cursor control is restored to being normal!