Compatibility boundary

Kimi-native first, inspired by oh-my-codex—not a blind copy.

oh-my-kimi borrows the idea of an “oh-my-*” enhancement layer, but it is being shaped specifically for Kimi CLI. That means some concepts are inherited, some are adapted, and some are intentionally left out.

Kimi-native surfaces

  • Primary package name: oh-my-kimi
  • Primary command name: omk
  • Public docs and website branding
  • Kimi CLI-first positioning and shell language

Inherited ideas

  • Workflow-shell model inspired by oh-my-codex
  • Setup + skills + team + state as the main shell pieces
  • Project attribution to the upstream design work
  • Porting decisions documented instead of hidden

What this site wants you to understand

oh-my-kimi should be read as “an enhancement layer for Kimi CLI,” not as a generic multi-agent site and not as a silent rename of another project. That distinction is the main compatibility story.