@andrewhmir/dsh-btw

LIMITATIONS

Known limitations

- **In-flight partial assistant text is not included.** The snapshot reads the committed session surface; while the main turn is streaming, the current assistant message is not committed yet. `/btw` sees the conversation as of the last committed event. - **Not visible in session-log cost dashboards.** Ephemeral calls leave no session-log trace; provider billing is the source of truth for them. - **Web GUI only.** The host route is generic, but the invocation and the card are client-side Web features. - **English card copy.** Display metadata ships in English and Chinese; in-card strings are English in this version. - **A future host `btw` command would shadow this plugin.** The host catalog is adjudicated before the plugin's source; if a future harness version ships a host command with the same name, `/btw` would execute that command instead. - **Single-shot.** There is no follow-up turn inside the card; automatic continuations only finish the same answer. - **Continuations are bounded.** After `continuations` rounds a still-truncated answer is shown with a "still cut off" note rather than continuing forever. - **The card floats above the chat** (bottom-right). It does not reflow the conversation, so on a very small viewport it can overlap the composer area; the × button and Escape-while-focused remain available.