Descriptions:
Ray Amjad walks through one of Claude Code’s newest quality-of-life features: the `/btw` command, a built-in side channel that lets developers ask questions mid-session without interrupting the active coding workflow or polluting the conversation history. The core problem it solves is well-explained — every time a developer interrupts Claude Code with a question, they break the agent’s flow, inject noise into the context window, and can degrade future outputs if done repeatedly.
The tutorial demonstrates `/btw` in action, showing how it answers questions inline while the main session continues working in the background. Because it draws on the prompt cache of the active session, the cost of asking questions is low. The trade-offs are clearly laid out: `/btw` is single-turn only and has no tool access, making it best for quick questions. For deeper dives — generating Mermaid diagrams, reading additional files, or exploring alternative implementation paths — the older `–fork-session` approach or the `/fork` command remains the better choice.
Amjad ties together the full suite of Claude Code session management tools, including how to run parallel branches on separate git worktrees and when to use each approach. The video is one of a series covering advanced Claude Code workflows and references his earlier technique of splitting terminal windows with `claude -c –fork-session`, which this new feature partially replaces for the most common use case.
📺 Source: Ray Amjad · Published March 11, 2026
🏷️ Format: Tutorial Demo
