kimaki CLI
kimaki turns Discord into a control surface for OpenCode: every channel is a project, every thread a separate coding-agent session.
- 1,449 ★ on the repository
- Last commit
- MIT
Broad access
Why this level
- A Discord thread message triggers code edits right on the user's machine through OpenCode, with access to the project's filesystem.
Install
- Works in
Manual install
npx -y kimaki@latestThe CLI walks through installing the Discord bot and creating channels for projects; setup takes about a minute.
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- A Discord thread message triggers code edits right on the user's machine through OpenCode, with access to the project's filesystem.
This is third-party code. Review the repository files before installing.
What it does
kimaki connects Discord to the OpenCode agent: a server channel becomes a project linked to a folder on the user's machine, and every thread is a separate OpenCode session. A message in a thread triggers the agent to edit code right on that machine, without mixing different tasks into one conversation stream, the way tools that pile everything into a single channel do. The bot installs to a Discord server in one click through the CLI, which walks you through setup: choosing projects and creating a channel for each. OpenCode version 2 is required, and if it is missing, kimaki installs it automatically the same way OpenCode itself does.
Who it is for. OpenCode developers who want to run and switch coding-agent sessions right from Discord without a terminal at hand.
Good fit when
- Several projects need running in parallel, each in its own channel, with no mixing of tasks.
- Switching between a project's tasks should follow threads, not one shared feed.
- Code edits need triggering right from a Discord message while no terminal is at hand.
- OpenCode is already in use, or installing it automatically through kimaki is acceptable.
Not a fit when
- A coding agent other than OpenCode is needed: kimaki installs and connects specifically that one.
- Discord is unacceptable as a control channel under workspace or team policy.
- Task isolation matters without separate threads per session inside one shared channel.
Example request
Open a thread in my project's channel and ask the agent to fix the failing test in auth.ts.Limitations
kimaki works specifically with OpenCode 2: if OpenCode 1 is installed, it needs upgrading first with the same install script. Code is edited right on the machine running kimaki, giving the agent access to that project's filesystem. The "channel is a project, thread is a session" mapping is a fixed structure: mixing several projects into one channel without confusion is not possible. The Discord bot needs permission to create channels and threads on the server during first setup.
How to disable. Remove the bot from the Discord server and stop the CLI process; for full removal, run `npm uninstall -g kimaki` if it was installed globally.
FAQ
How do I start setup?
Run `npx -y kimaki@latest`; the CLI walks you through installing the bot to Discord and creating channels for projects.
Do I need to install OpenCode separately?
No, if OpenCode is missing, kimaki installs it automatically the same way OpenCode itself does; OpenCode 1 needs manually upgrading to 2.
How are a project's tasks kept separate?
Every message sent opens a thread that becomes its own OpenCode session, so tasks never mix into one shared feed.
How does this differ from other Discord agent bots?
Other tools pile every session into one channel; kimaki splits projects into channels and sessions into threads, giving each task its own place.
Where do code edits happen?
Right on the machine running kimaki, in the project folder linked to that channel.
Discussion
No questions or reviews yet.
Related
CLI toolsTen Claude Code commands that run Codex and Gemini as helpers: Claude plans, Codex writes code, Gemini reviews and reads mockups
Kimi Bridge for Claude Code
kimi-bridge
An MCP server that turns a local Kimi Code CLI into a second agent inside Claude Code, with a dedicated BSL review tool for 1C
Kode CLI is a terminal coding agent that reads AGENTS.md and CLAUDE.md, connects MCP servers and works with many models.
A Telegram bot for OpenCode: send coding tasks, watch progress and switch models from your phone while OpenCode keeps running on your own computer
A desktop board turns a card into an agent session in its own git worktree, flags the agent waiting on you, offers an MCP server
A terminal coding agent in Go: GLM, DeepSeek and local Ollama models, 59 built-in tools and MCP
README in short
The author invites trying the bot on the project's own Discord server to see how it works before installing it on your own server.