[Bug] Most build-in Slash Commands Not Working in VS Code Extension 2.0.x
Bug Description After updating to Claude Code extension 2.0.x (now on 2.0.5 ) in VS Code, most built-in slash commands no longer work. For example, when I type /help or /rewind in the Claude input box, I only see “no matching commands”. No dropdown or command execution happens. in the vs code claude terminal i do get those commands there they work fine only in extension they dont appear.
Environment: VS Code: latest stable release (e.g. 1.104.2) Claude Code Extension: 2.0.5 OS: Windows 11
Steps to Reproduce: Install Claude Code extension v2.0.5. Open the Claude chat panel in VS Code. Type /help or /rewind. Result: “no matching commands” instead of showing the built-in command list.
Expected Behavior: Typing /help should show the available built-in commands. Typing /rewind should rewind the conversation.
Troubleshooting Tried: Verified VS Code is on the newest version. Uninstalled/reinstalled VS Code with cleanup Uninstalled/reinstalled Claude Code extension.
Current Result: Slash commands like /help and /rewind don’t work, always showing “no matching commands”.
Request: Could you confirm if this is a known bug in 2.0.5? And is there a workaround or upcoming fix so that built-in slash commands become available again?
Environment Info
- Platform: win32
- Terminal: vscode
- Version: 2.0.5
- Feedback ID: 44e3ac39-f887-4595-80c7-c5b9a4332713
Errors
[]
see here a small batch of available commands.
Found 3 possible duplicate issues:
- https://github.com/anthropics/claude-code/issues/8569
- https://github.com/anthropics/claude-code/issues/8590
- https://github.com/anthropics/claude-code/issues/8503
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
same issue with me, there and rewind is a really important one too
- This a serious issue. I just want to know if this is being worked on.
- The bot tags it as properly a bug yet it threatens to close it as a duplicate? That's a very mixed message.
- How are we supposed to know, if this is the right bug to watch for progress on fixing it.
- Still an issue in vscode extension version 2.0.9
Same problem for me, I don't see rewind or agents commands.
Cursor: Version: 1.7.33 VSCode Version: 1.99.3 Commit: a84f941711ad680a635c8a3456002833186c4840 Date: 2025-10-03T03:28:06.574Z Electron: 34.5.8 Chromium: 132.0.6834.210 Node.js: 20.19.1 V8: 13.2.152.41-electron.0 OS: Darwin arm64 24.4.0
Claude Code for VS COde version 2.0.1
Feedback ID: 960548a4-e892-4008-beaf-13ef8fd86673 (sent from CLI version where it seems to work fine)
Same for me with m1 mac
In my vs code, it does not work in claude code extension but it works if I run slash commands in terminal inside vs code
In addition to slash commands missing, I can no longer run ANY custom commands that I have created. Falling back to running claude in a terminal inside vscode to have a working environment.
MacOS 15.7.1 VS Code 1.104.3 Claude Extension 2.0.10
Same in Ubuntu.
Same issue here. Win10, Cursor/VSC, multiple computers, version 2.0.13.
Commands show up in terminal version.
The CLI doesn't show slash commands in its help - they're runtime features. Let me check the critical debug output again from your log: [DEBUG] Slash commands included in SlashCommand tool: This line appears but is EMPTY! The backend is trying to send slash commands to the SlashCommand tool, but the list is empty.
This is definitely a bug Given that: It happens on multiple machines The backend loads successfully but provides zero slash commands The CLI (terminal) version works fine
Same Here ! m1 Mac Os26.0.1 Claude Code for VS Code Version 2.0.21 VS Code 1.105.1
Custom slash commands don't show up for me in VSCode extension 2.0.24. I verified that they were working in 2.0.14 and 2.0.20. CLI doesn't have the issue.
Same here. Commands are broken after VS Code update: Version: 1.105.1 (Universal) Commit: 7d842fb85a0275a4a8e4d7e040d2625abbf7f084 Date: 2025-10-14T22:33:36.618Z Electron: 37.6.0 ElectronBuildId: 12502201 Chromium: 138.0.7204.251 Node.js: 22.19.0 V8: 13.8.258.32-electron.0 OS: Darwin x64 25.0.0
These entries which open in the terminal started appearing for me in 2.0.24 (or .23), but there are still some missing.
neither /rewind nor double esc works for me when trying to use checkpoint in 2.0.x GUI extension. are you guys also having issue with double esc?
neither /rewind nor double esc works for me when trying to use checkpoint in 2.0.x GUI extension. are you guys also having issue with double esc?
/rewind has never appeared as a slash command for me in the IDE extension.
I see in other video's on youtube people using it. also the extension without all the cli / commands is a no go. I do like the extension because it solves copy pasting the photos. which now freezes my cli in vs code.
2.0.42 same problem
I'm now even more confused if the extension misses feature parity with cli or its a bug. It would be good if Atrophic is transparant about it.
I'm now even more confused if the extension misses feature parity with cli or its a bug. It would be good if Atrophic is transparant about it.
It's far from parity, and I'm not sure it ever really can be, but I agree the differences/limitations should be clear.
Reducing the # of commands that require opening the terminal should be a goal too as it's clunky/buggy.
e.g. Why is it opening a new VSCode window instead of using the terminal in the existing one? 🤷♂️
I think UI integration is necessary especially for /rewind, CC is the only one among the extensions I use that lacks this feature.
I think UI integration is necessary especially for /rewind, CC is the only one among the extensions I use that lacks this feature.
I remember in many promotional materilas it is shown that this exists for GUI -- and for many friends of mine they also have it working properly, but I just don't have it -- no matter if I go on mac/windows/linux, or if its vscode or cursor
It is hard to believe that they still haven't realized the issue or that they don't have the ability to fix it -- it makes me wonder if it is the case that claude is intentionally having it as a limitation to some accounts
I'm from China by the way, even though I'm not living in China at the moment.