Kimi CLI
The core CLI still does the actual agent execution, prompting, and session work.
oh-my-kimi gives Kimi CLI a stronger shell around the core agent experience: setup, skills, repeatable workflows, team execution, runtime helpers, and durable local state. If you have seen projects like oh-my-codex or oh-my-claudecode, this is that kind of layer—but built for Kimi CLI.
/skill:ralplan, /skill:deep-interview, /skill:team, and /skill:ralph. The $name shorthand is OMK-style syntax and is not guaranteed by Kimi itself.
The core CLI still does the actual agent execution, prompting, and session work.
Adds setup, skills, docs, runtime helpers, team workflows, and a more opinionated day-to-day shell.
Similar idea, different target CLI: this fork is specifically shaped around Kimi CLI usage.
Use the same planning, execution, and verification flow every time instead of improvising prompts from scratch.
Get a more complete Kimi CLI environment with setup, doctor, skill scaffolding, and a documented default path.
Layer in tmux teams, HUD, MCP, notifications, and state tracking without rebuilding the shell yourself.
Plans, logs, runtime state, and workflow artifacts live locally so sessions remain durable across work days.
npm install -g oh-my-kimiomk setupomk doctoromkThat gets you from install to a Kimi-first workflow shell in minutes.
oh-my-kimi is opinionated about how work should flow once you are inside Kimi CLI.
$deep-interview "clarify the task"
/skill:ralplan approve the implementation plan
/skill:ralph drive it to completion
/skill:team 3:executor "parallelize the approved work"
oh-my-kimi is a Kimi-first fork built on top of oh-my-codex. The original project and upstream orchestration design are credited to Yeachan-Heo.
This fork is maintained by hao (wang-h).
The migration, branding, and adaptation work for oh-my-kimi was completed on top of the oh-my-codex foundation,
with substantial execution help from OpenAI Codex / Codex CLI workflows.
Read the public documentation map for the Kimi CLI enhancement layer.
See the reusable workflows that make oh-my-kimi feel productized.
Connect MCP, notifications, GitHub, and supporting runtime tooling.
Understand what is Kimi-native, what was inherited, and what is intentionally out of scope.