btw (side questions)
btw forks the current session's full context into a new thread and immediately answers a side question there, without disturbing the running task. Use it when you need a clarification in parallel.
The problem it solves
The agent is in the middle of a long task and you suddenly want to ask "wait, why did you choose X?" If you send that in the thread, it interrupts the work. If you wait, you lose the moment.
btw splits the question off into its own thread that shares the same context but runs independently.
thread: build ──────────────────────▶ keeps working │ │ ". btw why pick?" ▼ thread: btw ──▶ answers in parallel
Using btw
Two equivalent triggers:
/btw <prompt>— fork and ask the prompt.. btwsuffix — end a message with punctuation plusbtw, for examplewhy this approach? btw. Supported forms include. btw,! btw, a trailingbtw., orbtwon its own final line.
Unlike the queue suffix, the
btw suffix requires punctuation or a newline before it, so btw fix this at the start of a message is not treated as a btw.What happens
- Kimaki forks the entire session context (no single message ID), so the new thread knows everything the original does.
- It creates a thread named
btw: <your prompt>. - It does not replay past Discord messages into the new thread; it just carries the context.
- It dispatches your question immediately, so the forked session starts answering right away.
The forked session is told its only job is to answer your question: it will not continue, resume, or reference the original task.
The original thread is never paused or interrupted. btw runs as a separate session in parallel.