What is Claude Code's /btw Command? Quick Guide
Problem
I’m working on a long coding session in Claude Code. Suddenly I have a quick question like “what’s the syntax for useEffect cleanup?” - but I don’t want to derail my main task or pollute my conversation history with tangential questions.
What /btw Does
The /btw command in Claude Code lets you ask quick side questions while your main task continues. The answer appears in an overlay that you dismiss with Escape, keeping your conversation history clean and your context unpolluted - no tokens wasted on full agent interactions.
Key mechanics:
- Answer pops up in an overlay
- Press Escape to dismiss
- Conversation history stays clean
- Doesn’t burn tokens on full agent interaction
- Uses Claude’s knowledge + your current session context only
- No tool access - keeps it lightweight
Version Requirement
You need Claude Code version 2.1.72 or higher for /btw to work.
Check your version:
claude --versionIf you’re below 2.1.72, update:
claude updateHow to Use /btw
The syntax is simple:
/btw <your question>Example: Quick Syntax Check
# During an active Claude Code session> /btw what's the difference between useMemo and useCallback?
# Answer appears in overlay# Press Escape to dismiss# Your main conversation remains cleanExample: Pre-Task Orientation
# Before starting a long task> /btw what's the typical pattern for handling authentication in Express.js?
# Get answer, dismiss with Escape# Now start your actual task with contextWhat /btw Does NOT Do
It’s important to understand the limitations:
| Limitation | What it means |
|---|---|
| No tool access | Cannot read files or run commands |
| One-shot Q&A | No back-and-forth conversation |
| No history preservation | The exchange is lost after dismiss |
| Uses session context only | Cannot access external resources |
When to Use /btw vs Normal Prompts
Use /btw when:
- Quick syntax checks: “What’s the flag for verbose output in npm?”
- Concept clarifications: “What does ‘as const’ do in TypeScript?”
- Mid-task orientation: “What’s the pattern for error handling here?”
- Pre-task sanity checks: “Is this the right approach?”
Use normal prompts when:
- The question relates directly to your current task
- You want Claude to remember the answer
- You need Claude to use tools (read files, run commands)
- The exchange is part of the decision trail you want to preserve
The Origin
The /btw command was built by Erik Schluntz from Anthropic as a side project. The Reddit community response was enthusiastic - the top comment with 126 upvotes noted:
“Ah man, this is a gift to us Claude Code homies that have the ADHD brain”
This highlights the real problem /btw solves: context switching friction that can derail productive sessions.
Summary
In this post, I explained the `/btw command in Claude Code - a lightweight way to ask side questions without polluting your conversation history. The key point is that /btw gives you quick answers without the overhead of a full conversation exchange, keeping your context window clean and focused.
Final Words + More Resources
My intention with this article was to help others share my knowledge and experience. If you want to contact me, you can contact by email: Email me
Here are also the most important links from this article along with some further resources that will help you in this scope:
Oh, and if you found these resources useful, don’t forget to support me by starring the repo on GitHub!
Comments