Claude Code CLI’s @ file autocomplete (a dropdown that suggests files as you type) does not appear in Cursor’s integrated terminal. The @ character is typed but no suggestion dropdown is rendered.
The same CLI binary, same WSL2 instance, same project — the @ autocomplete works in:
VS Code’s integrated terminal
A standalone terminal (Ubuntu/WSL launched from PowerShell)
Only Cursor’s integrated terminal is affected. This suggests Cursor’s terminal emulation handles something differently that prevents the autocomplete UI from rendering.
Note: this is not the Claude Code extension — this is the Claude Code CLI (claude) run directly in the integrated terminal.
Steps to Reproduce
On Windows, open Cursor connected to WSL2 (Ubuntu)
Open the integrated terminal (zsh)
Run claude to start a Claude Code CLI session (v2.1.29, native install)
Type @README or any partial filename
Result: no autocomplete suggestions appear — the @ character is shown but no dropdown
Now open VS Code connected to the same WSL2 (Ubuntu)
Open the integrated terminal, run claude, type @README
Result: autocomplete suggestions appear correctly
Same binary, same shell, same WSL — different result in Cursor vs VS Code.
Expected Behavior
Typing @ in the Claude Code CLI prompt should display a file autocomplete dropdown with matching suggestions, as it does in VS Code’s integrated terminal and standalone terminals.
Hey, thanks for the report. This looks like a bug in Cursor’s terminal emulation, since the same binary works in the same WSL2 setup in VSCode but not in Cursor.
From your description, the Claude Code CLI uses TUI elements like a dropdown menu for autocomplete, and something in Cursor’s terminal rendering is preventing those elements from showing up. This could be due to differences in how Cursor handles terminal escape sequences or ANSI codes compared to VSCode.
I’ll pass this to the team and include your reproduction steps and the VSCode comparison. Let me know if you find a workaround or if anything changes.
Also, could you check one thing. In Cursor Settings there’s an option terminal.integrated.gpuAcceleration. Try toggling it off or on depending on your current setting. Sometimes GPU acceleration in the terminal affects rendering of more complex TUI elements.
Did you guys add some weird agent chat memory as well? I re-ran the first message of the thread and it did something I had previous chatted with it about that it should have dropped from context because I went back up before it.
Try 1: Ctrl+Shift+P > Preferences: Open Settings (UI) and searched and found terminal.integrated.gpuAcceleration. It was on auto. I didn’t change it.
Try 2: Project > .vscode/settings.json I changed it here, toggled off, my terminal jiggled a bit. Then tried the “@” and it worked. Then commented it out, tried the “@” again and it worked.
Truly though, I think… I think it might have just been me. In Claude Code > /preferences > “Respect .gitignore in file picker” was set to FALSE. So in the pic in the above, it was searching through everything in .venv too.
Then the question is, if thats the problem and its set to false why did it start working? Well I noticed “@” would intermitadly work. Maybe it was too busy indexing. I actually have no idea.
But in the end:
I’ve removed your setting
I’ve set CC > /config > “Respect .gitignore in file picker” == True
and the “@” is back again.
Thank you
EDIT:
(and to add… because there’s always more detail to the story - when I moved over to the non NPM version of CC - I did a big ~/.claude cleanup, it was about 20 GB. So I think it had cached all the node_modules and venv directories. I deleted them and the “@” stopped working because “Respect .gitignore in file picker” was set to False. Well that’s my theory anyhow)
This issue started exactly once I had actioned Claude Code’s display message to:
