Agent-readable docs index: /llms.txt. Full docs in one file: /llms-full.txt. Download /docs.zip to grep all markdown files locally.

btw (side questions)

btw forks the current session's full context into a new thread and answers a side question there. The running task in the original thread continues.
why did you pick zod here? btw

The problem it solves

The agent is in the middle of a long task and you want to ask "wait, why did you choose X?" A normal message in the thread interrupts the work. If you wait, you lose the moment.
btw sends the question to its own thread. That thread has the same context but runs independently.
  thread: build ──────────────────────▶ keeps working
       │
       │ "why pick? btw"
       ▼
  thread: btw: why pick? ──▶ answers in parallel

Using btw

There are two triggers with the same result:
  • /btw prompt:<question>: fork and ask the question.
  • btw suffix: end a message with punctuation plus btw, for example why this approach? btw. Supported forms are . btw, ! btw, ? btw, , btw, a trailing btw., or btw on its own last line.
The suffix needs punctuation or a newline before it. btw fix this at the start of a message is a normal message.
btw queue at the end (for example check the logs. btw queue) also forks at once. A queued fork is not supported.
btw only works in a session thread. In a project channel there is nothing to fork, so the message starts a normal new session.
From the CLI, use kimaki send --thread <id> --prompt 'why this approach? btw' or kimaki session btw <text>.

What happens

  1. Kimaki forks the whole session with OpenCode. The fork keeps the history, agent, model and instructions.
  2. It creates a thread named btw: <your question> and adds you to it.
  3. The first message in the new thread is Reusing context from #original-thread to answer prompt... followed by your question.
  4. It sends your question at once, so the fork starts to answer.
  5. Where you asked, Kimaki replies Session forked! Continue in #btw-thread.
The forked session gets an instruction to only answer your question. It does not continue the original task.
Attachments on a suffix message go to the fork with the question.
The original thread is not paused or interrupted. Its pending questions and permission requests stay open.

btw vs fork vs queue

Want to...Use
Ask a side question in parallel, keep the run goingbtw
Continue from a specific earlier message/fork
Add a follow-up for after the run finishesthe queue
Redirect the agent right nowa normal message