06. Sessions
Ask aside with /btw
Sometimes the assistant is mid-turn and you need a short answer that must not cut in: a type name, a second look at error handling, “what does this flag do?” /btw sends that side question on its own path. The current task keeps running.
Send a side question
/btw <question>The question is required. An empty /btw is an error.
/btw also check the error handling
/btw what is the return type of parse_config?/btw is session-scoped and only works with an active session. Without one, the TUI says **No active session**.
The aside bypasses the prompt queue. You can send it while the assistant is busy. It does not cancel the current turn, and it is not lined up behind queued prompts.
What happens on screen
- The prompt text is cleared once the aside is sent.
- A panel opens above the prompt: your question, then a loading state.
- When the answer arrives, the panel stays until you dismiss it.
- Press **Esc** to close it. A finished answer is saved into scrollback as a collapsed
/btwblock. A late reply after you already dismissed the panel is dropped.
The panel does not block the main conversation. You can keep reading the running turn. In fullscreen, focus moves to the panel when the answer is ready; Esc dismisses /btw before it does anything else (for example, backing out of the dashboard).
In **minimal** mode (--minimal / /minimal) the same idea holds: the answer appears in a dismissible panel above the prompt; Esc dismisses it; a finished answer is written into native scrollback.
What `/btw` is not
/btw | A normal prompt |
|---|---|
| Does not interrupt the current turn | Becomes the next turn (or queues) |
| Side question + answer are not part of the main turn | Adds a rewind point and uses the main context |
| Esc dismisses the panel | Esc cancels or leaves, depending on state |
Use /btw for a glance. Use a normal prompt when the answer should steer the rest of the session. Use /rewind if a main-turn reply went wrong.