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

Use the OpenCode TUI with Kimaki sessions

Kimaki does not run its own OpenCode server. It uses the OpenCode 2 background service of your machine, the same server the OpenCode TUI and CLI use. So a Kimaki session is a normal OpenCode session.
Run /session-id in a thread. Kimaki replies with the session ID and the command to open it:
opencode /path/to/project --session ses_abc123
  Discord thread ──▶ kimaki bot ──┐
                                  ├──▶ OpenCode 2 service (opencode serve --service)
  terminal ──▶ opencode TUI ─────┘         one server, same sessions

Bring a TUI session into Discord

A session you started in the TUI can move into a Discord thread. Run /resume in the project channel and pick the session, or use the CLI:
kimaki session resume <session-id>

On a VPS

By default the TUI connects to the service of the same machine. SSH into the VPS and run opencode there:
ssh my-vps
opencode /path/to/project --session ses_abc123
Do not expose Kimaki's lock port (KIMAKI_LOCK_PORT, default 29988) to the network.

Manage the service

The service belongs to OpenCode. Use the OpenCode CLI to manage it:
opencode service status
opencode service restart
When the service restarts, Kimaki reconnects by itself. kimaki status shows the OpenCode URL and version the bot uses.
Kimaki V1 started its own OpenCode server. The --opencode-hostname and --opencode-port flags, OPENCODE_SERVER_PASSWORD, and /restart-opencode-server are gone.