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

Managing Sessions

Every thread is a session, and Kimaki gives you commands to manage its lifecycle: pick up old sessions, branch off, and keep the context healthy.

Resuming and starting

/resume <session> ──▶ move a session of this project into a new thread (autocomplete)
/new-session      ──▶ start a fresh session with a prompt, optional files and agent
  • /resume <session>: run it in a project channel. Autocomplete lists the project's sessions, newest first, including sessions started in the OpenCode TUI. Kimaki creates a Resume: <title> thread, posts recent history, and streams new output there. A session has one thread: older threads of that session stop following it.
  • /new-session prompt:<text>: start a session in a new thread. files: attaches project files (comma separated, autocomplete), agent: picks the agent.
From the terminal:
kimaki session list                 # sessions of the current project, with status and tokens
kimaki session list --all --active  # busy sessions of every project
kimaki session sync                 # write transcripts of the last 14 days to ~/.kimaki/transcripts
rg -il "auth bug" ~/.kimaki/transcripts   # search them; the file name is the session ID
kimaki session resume <sessionId>   # same as /resume
kimaki session read <sessionId>     # print the conversation as markdown

Forking

Forking copies a session so you can explore without disturbing the original.
  • /fork: pick one of your earlier messages. The fork continues as if you had not sent that message.
  • /fork-subagent: pick a subagent session of this thread and continue it in its own thread.
  • /btw: fork the whole context into a btw: thread to answer a side question while the original keeps running.
The CLI equivalent is kimaki session fork [id], with --before <messageId> to fork before a message.
Use /fork to try an alternative approach from a known-good point. The original thread stays intact, so you can compare both.

Identifying and sharing

  • /session-id: show the session ID, the thread ID, and a command to open the session in the OpenCode TUI, like opencode /code/web-app --session ses_....
  • /diff: share the current git changes as a diff URL.
  • kimaki session url <id>: print the Discord URL of a session's thread.
To read the session's recorded events and file a Kimaki bug, see Debug sessions and report bugs.

Context management

Long sessions fill the model's context window. Keep them healthy:
  • /context-usage: show the tokens used, the percentage of the context window, the model, and the session cost.
  • /compact: summarize the conversation so far to free up context. Kimaki posts -# ⬦ context compacted when it is done.
The footer at the end of every finished turn also shows the context percentage:
-# *kimakivoice ⋅ main ⋅ 2m 30s ⋅ 71% ⋅ claude-opus-4-6*

Undo and redo

  • /undo: remove the last turn from the session. Run it again to go one more turn back. File changes are kept; revert them with git if you need to.
  • /redo: bring back the turn you undid, one step at a time.
Both stop the current run first.