What's New — Faithful summary of the source
Claude Code has introduced a /btw command that enables side-chain conversations while Claude is actively working on a coding task. This feature allows developers to ask follow-up questions, request clarifications, or provide additional context without interrupting the primary workflow. The command appears as a text input field that remains accessible during Claude's execution phase, creating a parallel conversation thread that maintains the original context.
This development comes as developers are increasingly hitting usage limits with AI coding tools during complex projects. One developer working on a kernel OS project (Linux-based, expanding to x86 with AI integration) reported hitting Claude Pro plan limits mid-session, which "kills the flow" of development. Another developer considering a $200/month subscription upgrade specifically mentioned wanting to "be building almost everyday of the month with Sonnet" without budget constraints interrupting their workflow.
How It Works — Technical details, API changes, workflow impact
The /btw command functions as a non-blocking communication channel. When Claude is processing a request—whether it's generating code, running tests, or analyzing a codebase—developers can type /btw followed by their question or instruction. This creates a separate conversation thread that doesn't reset the main task's context.
From the available screenshots and descriptions, the interface shows:
- A persistent text input field labeled for
/btwcommands - Clear visual separation between main task output and side conversations
- Context preservation across both conversation threads
This differs significantly from traditional chat interfaces where asking a follow-up question would either interrupt the current operation or require starting a new conversation with potentially lost context.
For developers working on complex projects like kernel development or large-scale refactoring, this addresses a specific pain point: the need to clarify requirements or ask about implementation details while Claude is in the middle of processing. Previously, developers would either wait for completion (breaking flow) or interrupt and risk context loss.
Practical Takeaways — What developers should do differently
Use
/btwfor clarification during long-running tasks: When Claude is generating multiple files or running complex analyses, use/btwto ask about specific implementation choices without stopping the process.Maintain context for complex refactoring: For large-scale code changes, use
/btwto provide additional constraints or ask about edge cases as you see them emerge in the generated code.Combine with agentic workflows: The
/btwcommand is particularly valuable when using Claude in agentic mode where it's autonomously working through multi-step tasks. You can guide the direction without taking full control.Budget-aware usage: Since Claude Code operates on usage-based pricing (with Pro plans having specific limits), the
/btwcommand can help maximize value by reducing the need to restart conversations when clarification is needed mid-task.
Broader Context — How this fits into the AI coding tools landscape
The /btw feature represents a shift toward more conversational, interruptible AI coding assistants. While Cursor has focused on tight IDE integration and browser automation capabilities (mentioned by users who appreciate its "seamlessly integrated" browser), Claude Code is optimizing for sustained, complex development sessions where context preservation is critical.
This development comes at a time when developers are actively comparing subscription options. The $200/month tier discussion highlights that serious developers are hitting usage limits and looking for solutions that support continuous, uninterrupted development. One developer specifically mentioned wanting to replace their Perplexity subscription for research tasks with a single $200 AI subscription that covers all needs.
For kernel and systems programming—mentioned in the source as a specific use case—the ability to maintain context during long compilation and testing cycles is particularly valuable. The developer working on x86 kernel expansion with AI integration represents exactly the type of complex, multi-hour session where /btw provides the most benefit.
Compared to Cursor's approach of offering unlimited Claude Sonnet usage (with some caveats), Claude Code's feature development suggests a focus on making each interaction more productive rather than simply providing more interactions. This aligns with the needs of developers working on complex projects where a single session might involve hours of back-and-forth with the AI assistant.
The Medium article from a junior developer who switched from Cursor to Claude Code mentioned "real problems, real solutions, real code"—suggesting that workflow improvements like /btw might be driving adoption among developers who prioritize sustained productivity over flashy features.
