[BUG] The /btw command is not working

Open 💬 17 comments Opened Mar 11, 2026 by dmm-l-mediehus

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?

_Tip: Use /btw to ask a quick side question without interrupting Claude's current work_

I then tried it while it was planning, I typed: "/btw test" but it did absolutely nothing, it didn't respond to the question while it was working.

<img width="1151" height="304" alt="Image" src="https://github.com/user-attachments/assets/c3f7555d-4fb3-4d3a-a788-48b28e4f3544" />

What Should Happen?

I expected it to answer the side question as it was working and does not interrupt the current work.

Here's how it should have happened:
https://x.com/trq212/status/2031506296697131352

Error Messages/Logs

Steps to Reproduce

  1. Plan
  2. Type: "/btw test" while it's planning
  3. Does not respond.

Claude Model

Opus

Is this a regression?

No, this never worked

Last Working Version

_No response_

Claude Code Version

2.1.72

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

Windows Terminal

Additional Information

_No response_

View original on GitHub ↗

17 Comments

github-actions[bot] · 4 months ago

Found 1 possible duplicate issue:

  1. https://github.com/anthropics/claude-code/issues/14804

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

laniakea001 · 4 months ago

This could be related to command parsing or keybinding conflicts.

Debugging Steps:

  1. Check if works in a fresh session (not just the current one)
  2. Look at keyboard shortcut configurations that might be intercepting the key
  3. Check if there are any custom skills or commands that might be shadowing built-ins

Potential Causes:

  • Custom keybindings taking precedence
  • A skill or command with higher priority intercepting the input
  • Input method editor (IME) interference on certain keyboards

Workaround:
Try using the full command syntax if available, or check if there's an alternative way to access the /btw functionality in the meantime.

qdba · 4 months ago

Costs me 27k Token claude-code searching for resolution. :-|

saagarjha · 4 months ago

I don't think I have ever had a slash command get responded to until Claude was done working, it seems like /btw works exactly the same way (in that it does nothing…)

boozedog · 4 months ago

same issue here. i had similar problem with /loop but that got fixed in https://github.com/anthropics/claude-code/issues/31759 ... gating problem

but running .73 today I still have no /btw command

much sad! such fomo! i probably should not watch so much youtube

boozedog · 4 months ago

Tested again today with .74 and /btw still does not work

I'm guessing it was gated like /loop was but not sure

boozedog · 4 months ago

<img width="310" height="167" alt="Image" src="https://github.com/user-attachments/assets/242e2ff4-ce2a-44b1-b8ee-94f9efdabe0d" />

Caleb-KS · 4 months ago

I was getting this too, but then it suddenly started working a few hours later.

royshonan · 4 months ago

I'm experiencing the same issue on v2.1.76 (macOS, Darwin 24.6.0).

Steps to reproduce:

  1. Open Claude Code CLI (v2.1.76, macOS)
  2. Type /b — no /btw candidate appears in autocomplete
  3. Type /btw directly — returns "Unknown skill: btw"

Tested on both Terminal CLI and Claude Code for Desktop — neither works.

The docs and in-app hints reference /btw, but the command is not available. It would be helpful to either ship the feature or remove the hints until it's ready.

Also, is /btw planned for Claude Code for Desktop? Would appreciate clarification on Desktop support.

Additionally, /feedback itself fails with "Could not submit feedback. Please try again later." — so I couldn't report this through the official channel (#10905, #12638).

jasonfong121-star · 4 months ago

same question,the version for me is Claude Code v2.1.77

<img width="233" height="79" alt="Image" src="https://github.com/user-attachments/assets/27d6542a-a13d-40c0-a8e6-13443ad11c8c" />

jasonfong121-star · 4 months ago

solved at this morning
my claude code version is v2.1.78
guys can update to the latest version and try the command

royshonan · 4 months ago

Confirmed that /btw is now working on v2.1.78 (macOS, Terminal CLI). Thanks for the fix!

That said, I'm still hoping to see /btw support come to Claude Code for Desktop as well. Would love to hear if there are any plans for that.

brendan-mcgill · 4 months ago

Running on Windows, claude code v2.1.78 and I still get the following when I try and use /btw:
Unknown skill: btw

jaxx2104 · 4 months ago

I found that having DISABLE_TELEMETRY set in the environment causes /btw to not appear as a command option. After removing this environment variable, /btw showed up correctly.

Elity · 4 months ago
I found that having DISABLE_TELEMETRY set in the environment causes /btw to not appear as a command option. After removing this environment variable, /btw showed up correctly.

My Solution

Check environment variables in these locations:

  • ~/.claude/settings.json → env section
  • <project>/.claude/settings.json → env section
  • Shell profile (~/.zshrc, ~/.bashrc, etc.)
  • Launch command (e.g. DISABLE_TELEMETRY=1 claude)

Remove DISABLE_TELEMETRY and CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC if present, then restart Claude Code.

boozedog · 4 months ago

OK so maybe this is the same as https://github.com/anthropics/claude-code/issues/31759

In https://github.com/anthropics/claude-code/issues/31759#issuecomment-4042808754 @bcherny mentions /loop being gated in the same way, but he seemed to indicate that this was being fixed.

Maybe a regression.

For many of us, disabling telemetry etc. is not an option due to enterprise environment etc.

mrjackyliang · 3 days ago

The /btw command no longer works. The requests merge back into the main thread.