Kimi Code

[Machine-seeded — pending review] This page is seeded from the English source and awaits native-language review per the i18n review gate.

Vendor: Moonshot Install name: kimi-code Status: GA Native config: <project>/AGENTS.md plus <project>/.kimi-code/.apothem/support/

Installation

apothem install --harness kimi-code --project /path/to/project

The adapter writes the shared Apothem governance surface into the project-root AGENTS.md as a sentinel-delimited managed block (operator prose outside the sentinels is preserved) and keeps the non-native Markdown cohorts under the Apothem-owned support tree at <project>/.kimi-code/.apothem/support/.

Kimi Code reads the project-root AGENTS.md instruction file following the universal AGENTS.md convention, and project configuration lives under <project>/.kimi-code/. The <project>/.kimi-code/mcp.json surface is operator-owned; Apothem names it but authors no entries.

Files written: <project>/AGENTS.md (managed block) and the commands, skills, hooks, agents, rules, and templates cohorts under <project>/.kimi-code/.apothem/support/.

Profile-to-native-config mapping

The adapter reads Apothem's shared profile and renders the project-root AGENTS.md instruction surface on every apothem install or apothem update run. The behavioral rules and governance corpus land in the managed block of AGENTS.md; the commands, skills, hooks, agents, rules, and templates cohorts are placed under .kimi-code/.apothem/support/ and referenced from the instruction surface, because Kimi Code exposes no matching native primitive for each of those cohorts yet.

Compatibility notes

Kimi Code reads AGENTS.md from the project root and recognizes .kimi-code/mcp.json as the operator-owned MCP surface; Apothem names that surface but authors no entries into it. The rendered instruction surface drives the project directly. Kimi Code exposes no statusline or output-style file surface, so those cohorts are not materialized.

Kimi Code runs on the Kimi model family from Moonshot; see the vendor configuration reference for the current model and configuration surface.

Verification

apothem verify --harness kimi-code --project /path/to/project

The verify command confirms that:

The native config exists at the expected path.
All mandatory fields from the shared profile are present.
The adapter-specific verification routine reports success.

Updating

apothem update --harness kimi-code --project /path/to/project

Re-derives the project-root AGENTS.md managed block and the support cohorts from the current shared profile state.

Uninstalling

apothem uninstall --harness kimi-code --project /path/to/project

Removes the native config files written by the adapter. The shared profile YAML and Apothem engine are unaffected.

Conformity gate

python -m apothem.conformity.gate --all .

Troubleshooting

Symptom	Fix
Config file not found	Re-run `apothem install --harness kimi-code --project /path/to/project`
Verification failed	Run `apothem update --harness kimi-code --project /path/to/project`, then verify again
Unexpected config content	Check `~/.config/apothem/profile.yaml` or `--profile PATH`, then re-run `apothem update --harness kimi-code --project /path/to/project`

Configuration knobs

Flag	Default	Description
`--dry-run`	`false`	Preview install without writing files.