[BUG] @ file autocomplete has become slow

Status Fixed / completed
Maintainer reply ✓ Yes — igorkofman
Activity 10 comments · opened Jun 14, 2025 · closed Jun 19, 2025
💡 Likely answer: A maintainer (igorkofman, collaborator) responded on this thread — see the highlighted reply below.

Environment

  • Platform (select one):
  • [x] Anthropic API
  • Claude CLI version: 1.0.24
  • Operating System: macOS
  • Terminal: Alacritty

Bug Description

Entering files with @ used to be snappy. Now it takes nearly a second for matching files to appear after you type @somepaththatshouldmatch

Steps to Reproduce

  1. Try to autocomplete a file with @
  2. See how it's very slow

Expected Behavior

It should be instant, like it used to be

Actual Behavior

It's slow

Additional Context

View original on GitHub ↗

10 Comments

raine · 1 year ago

I wonder if this has something to do with postgres mcp stuff having appeared in @ output also at the same time as this problem started.

raine · 1 year ago

1.0.22 is the last version without this issue. I hope it's fixed.

claude config set -g autoUpdaterStatus disabled
npm install -g @anthropic-ai/claude-code@1.0.22
lukaszciastko · 1 year ago

Same here. It also doesn't list ALL files, just some files. Even in a very small project.

bkolligs · 1 year ago

This is no longer working for me at all! The @ symbol doesn't allow me to navigate any files in the codebase.

leonardocouy · 1 year ago
This is no longer working for me at all! The @ symbol doesn't allow me to navigate any files in the codebase.

@bkolligs take a look on this comment

pdavidson · 1 year ago

It's a very jarring experience when the file list doesn't come up and/or my file is missing from the menu

igorkofman collaborator · 1 year ago

We've identified the issue and will have a fix out tomorrow in 1.0.30. Thanks for the report and your patience!

igorkofman collaborator · 1 year ago

The fix has been deployed - let us know if it's better after updating.

XiaTiaoQAQ · 1 year ago
The fix has been deployed - let us know if it's better after updating.

Thanks for the fix. It’s better now, though performance is still slightly behind version 1.0.22.

github-actions[bot] · 1 year 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.