/btw command silently ineffective — submitted content is lost, not executed or persisted

What happened

The /btw command is silently ineffective. Instructions submitted through /btw are never actually executed, and their content is lost afterward. This has happened multiple times, not as a one-off.

Observed behavior:

1. Invoke /btw with a prompt (typed or pasted instructions).
2. It enters a separate/modal context — the main conversation cannot be continued while inside it.
3. Pressing Esc returns to the main conversation, and the /btw content disappears entirely.
4. The instructions submitted via /btw are not executed, and the content is not recoverable — it is not persisted into the session, and on at least one occasion no trace of the invocation appeared anywhere (input history, session transcript, or on disk).

Impact

Work dispatched through /btw is silently dropped. The user believes a task has started when in fact nothing runs and nothing is saved. Because it leaves no trace, it is very hard to diagnose, and a separate agent session has no way to recover what was submitted — which reads, wrongly, as if the user "imagined" it.

Expected

/btw should either reliably dispatch its instructions and persist the content, or fail loudly. It must never silently discard user instructions.

Environment

• Claude Code 2.1.216
• macOS (Darwin 25.5.0)