Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix /btw slash command not available in VS Code extension [2 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#54602•Fetched 2026-04-30 06:41:08
View on GitHub
Comments
2
Participants
2
Timeline
6
Reactions
0
Author
Eric-SHENNONGSHIEric-SHENNONGSHI
Participants
Eric-SHENNONGSHIEric-SHENNONGSHIgithub-actions[bot]github-actions[bot]
Timeline (top)
labeled ×3commented ×2closed ×1

The /btw slash command works in the Claude Code CLI but is not available when using Claude Code via the VS Code extension.

Root Cause

/btw is useful for asking quick side questions without polluting the main conversation history (and avoiding re-billing the full transcript on each follow-up). VS Code extension users currently have to drop to the integrated terminal or start a separate session to get the same behavior.

RAW_BUFFERClick to expand / collapse

Summary

The /btw slash command works in the Claude Code CLI but is not available when using Claude Code via the VS Code extension.

Expected

/btw <question> should fork a single-turn side query from the current conversation context, the same way it does in the terminal CLI.

Actual

/btw is not recognized as a slash command in the VS Code extension.

Why this matters

/btw is useful for asking quick side questions without polluting the main conversation history (and avoiding re-billing the full transcript on each follow-up). VS Code extension users currently have to drop to the integrated terminal or start a separate session to get the same behavior.

Request

Port /btw to the VS Code extension to bring it to parity with the CLI.

extent analysis

TL;DR

The /btw slash command needs to be implemented in the VS Code extension to match the functionality available in the Claude Code CLI.

Guidance

  • Review the code differences between the CLI and VS Code extension implementations to identify why /btw is not recognized in the extension.
  • Verify that the necessary command handlers or event listeners for slash commands are properly registered in the VS Code extension.
  • Check if there are any specific VS Code extension APIs or constraints that might affect how slash commands are handled compared to the CLI.
  • Consider creating a feature request or issue in the relevant repository to track the implementation of /btw in the VS Code extension.

Notes

The implementation details of the /btw command in the CLI are not provided, so it's unclear what specific changes would be needed in the VS Code extension.

Recommendation

Apply workaround: Use the Claude Code CLI for now when needing the /btw functionality, as the VS Code extension does not currently support it.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#conversation history#latency issue#model loading#dependency error#configuration error

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix /btw slash command not available in VS Code extension [2 comments, 2 participants]