Claude's /btw Command Enables Parallel Communication During Tasks

Claude's New /btw Command for Parallel Interaction
Claude AI has introduced a /btw command that enables users to communicate with the AI while it's actively processing a task. This feature allows for parallel interaction without stopping the current execution.
The /btw command specifically addresses a common workflow interruption: instead of halting Claude's current run, users can ask questions, provide extra instructions, or clarify requirements while Claude continues working. This is particularly useful during long-running tasks where interrupting the workflow would be inefficient.
According to the source material, this functionality helps maintain workflow continuity when Claude is engaged in extended operations. The feature appears to be designed for scenarios where users need to provide additional context or ask follow-up questions without resetting the AI's current progress.
For developers using AI coding assistants, this type of parallel communication capability can reduce context-switching overhead. When working with AI agents on complex coding tasks, being able to interject clarifications or additional requirements without restarting the entire process can save significant time and maintain task momentum.
The source credits Thariq Shihipar for the video demonstration of this feature, though specific implementation details or version requirements aren't provided in the source text.
📖 Read the full source: r/ClaudeAI
👀 See Also

OpenClaw token usage investigation reveals configuration issues
A developer burned through their OpenAI Codex weekly subscription in 1.5 days and used Claude Code to identify configuration problems: Telegram bots firing on every message, web fetches returning raw CSS/JS, and orphan session files accumulating.
Slash Agent Start-Up Tokens by 60%: Clean Up Your Bot's Workspace
One developer dropped start-up tokens from 80k to 31k by having an LLM audit and restructure workspace files—removing bloat, deduplicating info, and organizing tool docs into separate files.

Cron Jobs with AI Fallback Can Incur Unexpected API Costs When Tools Hang
A user reported that a cron job in OpenClaw checking an email inbox every 10 minutes using himalaya burned through ~$60 in API credits when the IMAP connection started hanging, triggering Claude agents on each timed-out run despite instructions to only engage AI for inbound emails.

Enforcing Hard Guardrails for OpenClaw AI Agents: Approval Gating and Concurrency Limits
An r/openclaw user asks how to enforce hard rules like email approval and concurrency limits on a Discord-connected OpenClaw bot running Ollama with GLM. The answer: move enforcement outside the model's reasoning loop.