[BUG] @-file tab completion replaces entire prompt when slash command is present and filename starts with /

Status Fixed / completed
Reported on v2.1.116
Maintainer reply None cached
Activity 3 comments · opened Apr 21, 2026 · closed Apr 22, 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?

When a prompt begins with a slash command and you use the @ file finder to reference a file whose path starts with /, pressing Tab to autocomplete replaces the entire prompt minus the slash command with just the completed file path. In addition the file finder is stuck, it won't continue searching.

What Should Happen?

Tab should complete only the @/... token in place, leaving the rest of the prompt intact.

Error Messages/Logs

None

Steps to Reproduce

  1. Start a prompt with a slash command, e.g. /blueprint something
  2. Type @/ and begin typing a file path
  3. Press Tab to autocomplete
  4. The entire prompt minus the slash command is replaced with just the completed file path (e.g. /some/file.ts)

Claude Model

Sonnet (default)

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

2.1.116

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

Windows Terminal

Additional Information

_No response_

View original on GitHub ↗

3 Comments

github-actions[bot] · 5 months ago

Found 3 possible duplicate issues:

  1. https://github.com/anthropics/claude-code/issues/27572
  2. https://github.com/anthropics/claude-code/issues/32781
  3. https://github.com/anthropics/claude-code/issues/19499

This issue will be automatically closed as a duplicate in 3 days.

  • If your issue is a duplicate, please close it and 👍 the existing issue instead
  • To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

thomasnagashima-droid · 5 months ago

#27572 is the same but you closed it. So there isn't an active version of this, it's still a bug. The other 2 are different. Plus you closed them anyhow.

github-actions[bot] · 5 months ago

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.