### Preflight Checklist - [x] I have searched [existing issues](https://github.com/anthropics/claude-code/issues?q=is%3Aissue%20state%3Aopen%20label%3Abug) 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? The Claude Code VS Code extension (v2.0.1) displays a very limited and incomplete list of available slash commands when typing /. Many essential commands

Opus 4.5 says: You're absolutely right - that's a terrible UX. The whole point of a model picker is: - Quick switching per session - Running Haiku in one tab for simple stuff (cheap/fast) - Running Opus or Sonnet in another tab for complex work - Without diving into settings every time The workaround defeats the purpose entirely. You'd have to: 1. Change settings 2. Open new tab 3. Change settings again 4. Open another tab 5. Repeat forever What should exist: A model dr

[BUG] VS Code Extension has an incomplete slash command list compared to the CLI version

Status Open

Maintainer reply None cached

Workaround ✓ Mentioned in thread ↓

Activity 14 comments · opened Oct 1, 2025

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?

The Claude Code VS Code extension (v2.0.1) displays a very limited and incomplete list of available slash commands when typing /. Many essential commands for configuration, management, and advanced features that are present in the native CLI application (v2.0.1) are missing from the extension's UI. This significantly limits the functionality and configurability of the extension, forcing users to switch back to the terminal for many core tasks.

What Should Happen?

The VS Code extension should have feature parity with the CLI application regarding available slash commands. Typing / in the extension's prompt should reveal a comprehensive list of commands, similar to the one available in the terminal version, allowing users to fully manage their Claude Code experience from within the IDE.

Error Messages/Logs

No error messages are displayed. This is a feature parity/missing feature issue.

Steps to Reproduce

Install the latest Claude Code VS Code extension from the VS Code Marketplace.
Open the Claude Code sidebar in VS Code by clicking the Spark icon.
In the chat input at the bottom of the sidebar, type /.
Observe the short list of available commands (e.g., /analyze, /clarify, /code-review, /compact, /constitution, /context, /implement, etc.).
Install or update to the latest native Claude Code CLI application (v2.0.1 or newer).
Run claude in an external or integrated terminal.
In the prompt, type /.
Observe the much longer, comprehensive list of commands available.
Compare the list from the VS Code extension to the list from the CLI and note the large discrepancy.

Claude Model

Sonnet (default)

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

2.0.1

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

The discrepancy makes it difficult to manage the agent's configuration, view status, or use advanced features directly from the VS Code UI. The documentation notes that some features are not yet implemented in the VS Code extension, and this issue highlights the impact of that gap.

Screenshots Analysis:

The provided screenshots of the VS Code extension show a command list of approximately 15-20 commands.
The provided text output from the CLI version shows a list of over 40 commands.

Key Missing Commands include (but are not limited to):

/add-dir
/agents
/config
/cost
/doctor
/export
/hooks
/ide
/install-github-app
/login, /logout
/mcp
/memory
/model
/permissions
/rewind
/status
/statusline
/terminal-setup
/usage

View original on GitHub ↗

14 Comments

github-actions[bot] · 11 months ago

Found 2 possible duplicate issues:

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

zachlandes · 10 months ago

This is very annoying. I can't rewind

github-actions[bot] · 8 months ago

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.

bradtraversy · 8 months ago

This is the one thing keeping me from using this over the CLI all the time

socialfabrik · 8 months ago

Opus 4.5 says:

You're absolutely right - that's a terrible UX. The whole point of a model picker is:

Quick switching per session
Running Haiku in one tab for simple stuff (cheap/fast)
Running Opus or Sonnet in another tab for complex work
Without diving into settings every time

The workaround defeats the purpose entirely. You'd have to:

Change settings
Open new tab
Change settings again
Open another tab
Repeat forever

What should exist: A model dropdown in the webview UI header, or /model working like it does in terminal.

socialfabrik · 8 months ago

sorry if I put this under non-optimal location. This is related to the lack of ability to /model from non-CLI

bashu-shopify · 7 months ago

I also just discovered how many slash commands we don't have. I'd love to use /rewind in the extension, it's a huge loss

mark-zs · 7 months ago

Especially need /rename and --chrome

nebrius · 6 months ago

I'm looking for /export myself.

jonalexander · 6 months ago

Need --chrome.

arigon · 6 months ago

/rc or /remote-control is missing as well.

scihant · 5 months ago

No new commands such as /btw either. It's baffling to see such a core feature still not working on the extension. Looks like they have no intention of fixing this.

arizonawayfarer · 4 months ago

/feedback and /bug are missing as well

pmcnary · 1 month ago

Still present in 2.1.220, ~10 months after this was filed. Specifics, since the issue asks which commands are missing:

The extension registers 22 commands — none is feedback or export. /bug and /export appear zero times in either extension.js or webview/index.js, while the CLI binary of the same version contains both.

For contrast, /compact, /clear, /config, /agents, /mcp and /login do appear in the webview bundle — so this is a curated subset, not a build artifact.

strings -a .../claude-code/bin/claude.exe | grep -c -- '/export'                      # non-zero
grep -c -- '/export' ~/.vscode/extensions/anthropic.claude-code-*/webview/index.js     # 0

Practical impact beyond convenience: the extension is the surface where failures occur, and it offers neither a way to report them nor a way to extract the evidence — while transcripts are deleted after 30 days by default (#62476, #59248). No export, no reporting path, and a retention default that destroys the record is a bad combination for anyone who needs to substantiate a problem later.