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

Images

Kimaki handles images in both directions. Attach images to your message for the agent to look at. The agent can upload image files back into the thread.

Sending images to the agent

Attach one or more images (or PDFs, or other files) to a Discord message. Kimaki downloads each file and gives it to the OpenCode session together with your text.
Discord attachment (png/jpg/pdf/...) │ download to <dataDir>/attachments/<messageId>/ ▼ file in the prompt ──▶ OpenCode session ──▶ model reads it
An image alone, with no text, is a valid message too.
Use this for screenshots of bugs, design mockups, error dialogs, or diagrams that you want the agent to implement or debug.
Kimaki does not resize or convert images. It sends the original file to OpenCode, and OpenCode applies its own image limits. If the model rejects a very large image, send a smaller screenshot.

Seeing images from the agent

When the agent makes image files (screenshots, generated diagrams, rendered output), it can upload them into the thread. Kimaki sends up to 10 files in one message, so Discord shows a set of screenshots together in a grid.
The agent uploads files with the Kimaki CLI:
kimaki upload-to-discord screenshot-1.png screenshot-2.png
Inside a session shell the session is known. From another terminal, add --session <session-id> (a session ID, thread ID or thread URL).
Images that a shell command prints to the terminal are not sent to Discord. The agent must save them to a file and upload the file.

Common workflows

  • Bug from a screenshot: paste a screenshot of the broken UI and say "fix this".
  • Implement a design: attach a mockup and ask the agent to build it.
  • Visual verification: ask the agent to screenshot a running app (with a browser tool) and upload the result, so you can check it on your phone.
To view a live dev server in a real browser instead of static screenshots, see Tunnels.