[BUG] 🪲@ file autocomplete broken in Cursor terminal after npm → native migration

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 using Claude Code CLI (not the VS Code/Cursor extension) in Cursor's integrated terminal (WSL2), typing @ to reference a file does not show any autocomplete suggestions. The @ character appears but no file suggestion dropdown is displayed. The Claude Code extension is installed but not used — this is purely a CLI issue.

The same feature works correctly in:

• A standalone terminal (Ubuntu/WSL launched from PowerShell)
• VS Code's integrated terminal (same WSL2 setup, same native binary)

This is Cursor-specific — VS Code and Cursor both use xterm.js, yet only Cursor is affected.

What Should Happen?

What Should Happen?

Typing @ followed by characters should display a file autocomplete dropdown with matching file suggestions, as it does in standalone terminals.

Error Messages/Logs

No error messages — the @ character simply appears without triggering any autocomplete UI.

Error Messages/Logs

N/A - a silent monster.

Steps to Reproduce

1. Install Claude Code native version via claude install (migrating from npm version)
2. Open Cursor (VS Code fork) connected to WSL2 (Ubuntu)
3. Open the integrated terminal in Cursor
4. Run claude to start a Claude Code CLI session
5. Type @README or any partial filename
6. Observe: no autocomplete suggestions appear
7. Open PowerShell on Windows and launch Ubuntu (WSL)
8. Run claude and type @README
9. Observe: autocomplete suggestions appear correctly
10. Open VS Code connected to the same WSL2 (Ubuntu), open integrated terminal
11. Run claude and type @README
12. Observe: autocomplete suggestions appear correctly — the feature works in VS Code but not Cursor

Claude Model

Opus

Is this a regression?

Yes, this worked in a previous version

Last Working Version

v2.1.17 via npm. After running claude install, the native version was also v2.1.17 — @ autocomplete was immediately broken on the native build. Upgraded to v2.1.29 (latest) — no change, @ autocomplete still does not work.

Claude Code Version

2.1.29

Platform

Anthropic API

Operating System

Ubuntu/Debian Linux

Terminal/Shell

Cursor

Additional Information

• Cursor version: 2.4.27
• WSL2 Ubuntu, Claude Code installed natively via claude install
• Previously used npm-installed Claude Code where @ autocomplete worked in the same Cursor terminal
• TERM=xterm-256color, TERM_PROGRAM=vscode
• ripgrep v14.1.0 is installed
• /doctor reports no issues
• Troubleshooting attempted with no effect:
• Updated from v2.1.17 to v2.1.29
• Disabled Claude Code extension in Cursor (issue persists whether extension is enabled or disabled)
• Tested on both stable (v2.1.17) and latest (v2.1.29) channels — issue persists on both
• Launched with TERM_PROGRAM=xterm claude
• Launched with VSCODE_INJECTION=0 claude
• Ran inside tmux within Cursor's terminal
• Works in VS Code integrated terminal (same WSL2, same native binary) — issue is Cursor-specific, not a general xterm.js problem
• Suggests the native binary's terminal rendering has a compatibility issue specific to Cursor's terminal implementation

Migration Steps Followed

Originally installed Claude Code via npm in May 2025. Migrated only because Claude Code continually showed this message on every launch:

Claude Code has switched from npm to native installer. Run claude install or see <https://docs.anthropic.com/en/docs/claude-code/getting-started> for more options.

Followed these exact steps:

1. cp -r ~/.claude ~/dot-claude-backup
2. Ran claude install (installs the native version)
3. Ran npm uninstall -g @anthropic-ai/claude-code to clean up the old npm package
4. Ran npm list -g @anthropic-ai/claude-code to verify the npm package is gone
5. Ensured ~/.local/bin is in PATH
6. Verified with claude --version and claude doctor

The @ autocomplete worked before this migration in the same Cursor integrated terminal with the npm version.