[BUG] @ file autocomplete does not open when editing a prompt recalled from history

Status Open
Reported on v2.1.233
Maintainer reply None cached
Activity 1 comment · opened Aug 17, 2026

Preflight Checklist

  • [x] I have searched existing issues and this hasn't been reported yet
  • [x] This is a single bug report
  • [x] I am using the latest version of Claude Code

What's Wrong?

When I recall a previous prompt from history with the Up/Down arrow keys and then edit
that recalled text, typing @ no longer opens the file reference suggestions. No
suggestion list appears, and the @ stays plain text, so the file cannot be selected
and referenced.

Typing @ in a prompt I type from scratch works normally in the same session, so the
recalled-prompt state is what makes the difference.

What Should Happen?

Typing @ in a recalled prompt should open the file search suggestions exactly as it
does in a freshly typed prompt, and selecting an entry should insert the file reference.

Error Messages/Logs

None. No error is printed, the suggestion list simply never appears.

Steps to Reproduce

  1. Start claude in any project directory.
  2. Submit a prompt, for example hello, so it is stored in the prompt history.
  3. At the empty input, press the Up arrow key to recall that prompt.
  4. Edit the recalled text, for example append a space and some words.
  5. Type @ to reference a file.
  6. No file suggestion list appears. Typing the beginning of a known file name after the

@ does not bring it up either.

For comparison, typing @ in a prompt typed from scratch in the same session opens the
suggestions as expected.

Claude Model

Opus

Is this a regression?

Yes, this worked in a previous version

Last Working Version

Unknown

Claude Code Version

2.1.233 (Claude Code)

Platform

Anthropic API

Operating System

Other Linux (Ubuntu on WSL2, kernel 6.18.33.1-microsoft-standard-WSL2)

Terminal/Shell

Windows Terminal (bash inside WSL2)

Additional Information

Not yet checked, so possibly relevant for narrowing it down:

  • whether / slash command suggestions have the same problem on a recalled prompt
  • whether clearing the input and retyping the text restores the suggestions
  • whether it also happens when the recalled prompt is left unedited

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗