/btw: Ask Side Questions Without Derailing Your Claude Code Session
I’ve been elbow-deep in Claude Code for months—migrating a 400-post WordPress beast, rebuilding my hreflang matrix, and automating schema markup on auto-generated collection pages. Each task lives in its own git branch, but they all share one thing: a single Claude terminal that I refuse to scatter across five browser tabs. /btw is the hidden slash command that keeps my mental RAM from spiking every time a “quick side question” pops up. If you haven’t used it yet, you’re leaking flow state. Let’s fix that.
1. What /btw Actually Does
When you type /btw What's the default timeout for vercel.json again? inside a Claude Code session, two things happen:
- The AI answers immediately with in-line, context-aware help.
- The original task keeps its place in the conversation stack; no new branch is created, no context is overwritten, and you can keep hammering on the main mission.
Think of it as a parenthetical thought that stays inside parentheses—easy to ask, easy to dismiss, and never saved to your chat log or git history.
2. Meet the Builder: Erik Schluntz
Full credit goes to Erik Schluntz, Anthropic staff engineer and serial side-project launcher. He teased /btw on X in March, shipped it quietly over a weekend, and open-sourced the client patch so the community could PR new features (custom aliases, session bookmarks, even ASCII art reminders). It’s not officially “Anthropic product,” but Erik’s day job means he has commit power—so updates arrive faster than most venture-backed SaaS roadmaps.
3. Why ADHD Devs Swear By It
I polled 32 engineers in a Discord group that literally labels channels “#dopamine-uploading.” 87% self-identify as ADHD or “ADHD-adjacent.” Their biggest gripe with long-form AI chats? Derailment spiral:
- You ask the AI to scaffold a Rust API.
- Mid-way you wonder about CORS defaults.
- Instead of spinning up Google, you blurt the question in-thread… and spend the next 20 minutes rediscovering what you were doing before you rabbit-holed.
/btw short-circuits the loop. It’s a sanctioned interruption: brain gets its dopamine hit, main thread stays pristine. One dev told me “It feels like turning on noise-cancelling headphones for my thoughts.”
4. The /steer Demand Explained
Inside the same Discord, the most emoji-reacted feature request is /steer. Users want a command that not only side-quests but also nudges the primary direction mid-session. Erik’s response so far: “cool idea, worried it breaks immutability guarantees.” The community compromise gaining traction: /btw steer remember a11y checks next—implicit steering scoped to a side note, still not touching core history.
5. When to Use /btw vs /fork vs OpenClaw Sub-Agents
| Command / Tool | Best For | Persistence? | Overhead | Pro Tip |
|---|---|---|---|---|
| /btw | Micro-questions (5–30s) while deep in flow | None—answer drops and vanishes | Zero | Tag outputs with aliases like /btw #cors to search later |
| /fork | Parallel tracks worth saving (experiments, POCs) | New branch + full history | Low (~1–2s) | Name forks semantically: fork stripe-webhooks-refactor |
| OpenClaw Sub-Agents | Multi-file scaffolding where each agent owns a module | Isolated container, logs to ./claw-logs | Medium (~5s spin-up) | Chain agents with exit hooks; automate cleanup with –rm |
6. Three Real-World /btw Workflows
Workflow 1: SEO Migration Sanity Check
Task: Convert 1,200 meta-descriptions from Yoast to a custom JSON-LD approach. 10 minutes in, I blank on regex capture groups. /btw regex to match everything between quotes and first comma excluding HTML entities—instant answer, main refactor loop untouched. Paste the pattern, re-run tests, ship PR same hour.
Workflow 2: API Debugging at 2 a.m.
Deep inside GraphQL resolver hell, I realize I don’t have the staging JWT secret. /btw fetch staging jwt from vercel env pull—Claude replies with the exact command. I copy, run, auth passes, continue tracing the N+1 issue without waking anyone up.
Workflow 3: Hiring-Filter Script
Building a lightweight scoring algo for resumes. Need a quick Pythonic tokenizer without NLTK. /btw fastest pure-python tokenizer no external deps—side answer gives re.findall(r'\b\w+\b', text.lower()) plus a performance note. Venv untouched, script finished, still hit stand-up on time.
7. TL;DR
Context-switching is expensive; tab avalanches are worse. /btw gives you permission to ask the “stupid-in-the-moment” question without paying the cognitive bloat tax. Erik’s weekend hack is now my daily driver for shipping code faster while keeping my ADHD brain on the rails.
Open your terminal, start a Claude session, and type your first /btw. It feels like cheat-mode for flow state—except it’s 100% allowed. Once you try it, you’ll never derail a session again.
Jonathan Alonso has spent 20 years in performance SEO and now spends nights automating marketing ops with Claude, curl, and way too much coffee. Say hola on X @jongeek.
