[BUG] /MCP command in VS Code extension breaks UI -

[Allmight97]

Environment

• Platform (select one):
  • [ ] Anthropic API
  • [ ] AWS Bedrock
  • [ ] Google Vertex AI
  • [ X] Other: VSCode/Cursor/Windsurf
• Claude CLI version: Version 1.0.11:
• Operating System: MacOS 15.5 (24F74)
• Terminal: VS Code/Cursor/Windsurf CC terminal interface

Bug Description

User text input panel disappears when typing /MCP - must hit escape to reveal the input area again. DOES NOT occur in WARP nor MacOS standard terminals.

Steps to Reproduce

1. Lauch CC in VS/Cursor/Windsurf Terminal
2. TYpe /MCP
3. You should see nothing and no indication of next steps.

Expected Behavior

Same output as standard terminals outside VS/Cursor/Windsurf - see attached pic.

Actual Behavior

Shows now other than last CC output - see attached pic 2.

[phj1081]

I can reproduce this issue.

Environment

• Windows 11 24H2 (Build 26100.4061)
• WSL 2 — Ubuntu 24.04.2 LTS (noble), kernel 5.15.167.4-microsoft-standard-WSL2
• claude-code CLI 1.0.16 (installed inside WSL)
• Node.js v22.16.0
• Terminals tested
  • VS Code Integrated Terminal
  • Warp v0.2025.06.04.08.11.stable_01

Steps to reproduce

1. cd ~/workspace/demo
2. Run claude to open the interactive REPL.
3. Type /mcp and press Enter.

Actual result The prompt and cursor disappear; input can be restored only by pressing Esc.
Ctrl-C does not recover the prompt.
Same behaviour in both VS Code Integrated Terminal and Warp.

Works fine when I move the repo to /mnt/c/Users/... and repeat the steps.

[msjoshlopez]

I am getting the same thing @phj1081

[github-actions[bot]]

This issue has been inactive for 30 days. If the issue is still occurring, please comment to let us know. Otherwise, this issue will be automatically closed in 30 days for housekeeping purposes.

[github-actions[bot]]

This issue has been automatically closed due to 60 days of inactivity. If you're still experiencing this issue, please open a new issue with updated information.

[github-actions[bot]]

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.