Skip to content

Add Kimi Code CLI as a compile/install target #2564

Description

Feature request

Add Kimi Code CLI (Moonshot AI's agentic coding CLI, kimi) as a supported target for apm compile / apm install, alongside the existing claude, codex, cursor, gemini, copilot, opencode, windsurf, and kiro targets.

Motivation

Kimi Code is a growing agent runtime with an open, file-based configuration model that maps very cleanly onto APM's primitives (instructions, agents, skills). Teams running multi-runtime setups currently have to hand-deploy APM packages to Kimi, which defeats the single-source-of-truth workflow APM provides for other runtimes.

Proposed target mapping

Kimi Code's discovery paths (from the official docs):

APM primitive Kimi Code destination (user/global) Project level
Instructions (AGENTS.md) ~/.kimi-code/AGENTS.md (moves with KIMI_CODE_HOME) project AGENTS.md / .kimi-code/AGENTS.md
Skills ~/.kimi-code/skills/ .kimi-code/skills/
Agents (sub-agent profiles) ~/.kimi-code/agents/ .kimi-code/agents/

Notes that make this low-effort:

  • Shared cross-client paths already exist: Kimi also reads ~/.agents/skills/ and ~/.agents/agents/ — the same shared ~/.agents/ convention APM already uses for the codex skills deploy, so skills may need no new deploy logic at all.
  • Agent file format is markdown + YAML frontmatter (name, description, tools, whenToUse, ...), and Kimi explicitly tolerates Claude Code-style agent files (comma-separated tools, unknown fields ignored, filename fallback for name). So existing .agent.md sources likely compile to Kimi profiles with little or no transformation.
  • Target detection marker: presence of a .kimi-code/ directory (consistent with how cursor/windsurf/kiro targets are detected).

References

Metadata

Metadata

Assignees

No one assigned

    Labels

    area/cliCLI command surface, flags, help text (cross-cutting).area/multi-targetMulti-target deploy spec, target directory creation, agent surface routing.priority/lowAccepted but not time-sensitivestatus/acceptedDirection approved, safe to start work.status/triagedInitial agentic triage complete; pending maintainer ratification (silence = approval).theme/portabilityOne manifest, every target. Multi-target deploy, marketplace, packaging, install.type/featureNew capability, new flag, new primitive.

    Type

    No type

    Projects

    Status
    In Progress

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions