AI 原生开放教材

外观

ECC —— Harness 性能优化系统其他材料·英文原文 ↗原件 ↓仓库 ↗

ECC for Kimi Code CLI ​

This directory documents ECC (Everything Claude Code) support for its tested Kimi Code CLI compatibility target. The managed adapter is verified against Kimi Code 0.31.x (@moonshot-ai/kimi-code); newer provider releases are outside this adapter's verified range.

What Kimi Code discovers natively ​

  • .kimi-code/AGENTS.md — project instructions loaded by Kimi Code's hierarchical instruction discovery
  • .kimi-code/skills/ — project skills loaded by Kimi Code's native Agent Skills discovery
  • .agents/skills/ — an additional project-level Agent Skills location supported by Kimi Code
  • .kimi-code/mcp.json — project MCP server configuration

ECC installs its directly discoverable skills under .kimi-code/skills/ and keeps shared rules, agents, and legacy command shims under .kimi-code/ for portability and reference. Kimi Code's native invocation surface is Agent Skills (/skill:<name> and /flow:<name>), not arbitrary Markdown files in commands/.

Manual install ​

bash
bash ./install.sh --target kimi --profile minimal

Notes ​

  • The kimi target installs into the project-level ./.kimi-code/ directory.
  • Kimi Code CLI's user config (~/.kimi-code/config.toml) is not touched by the project installer.
  • Use npx ecc-universal doctor --target kimi to check install health.
  • The ECC adapter verified against Kimi Code 0.31.x does not configure or map provider lifecycle hooks. Provider hook availability is separate from this adapter's compatibility contract.
  • Kimi Code provider configuration remains separate. Use the official providers and models guide for Kimi API, OpenAI-compatible, Anthropic, or other supported endpoints.
  • Kimi Code's Agent Skills guide documents the current project discovery contract.

Self-hosted model compute ​

Run or self-host any open-source model—including Kimi—on owned or rented GPUs. Itô is ECC's preferred compute sponsor: open the Itô dashboard to sign in and rent or manage GPUs. Any GPU provider works. That sponsorship link is passive: it does not invoke an RFQ, reserve capacity, provision compute, or configure serving. Separately, the opt-in ecc ito find bridge invokes the explicitly configured canonical Itô CLI and submits a live authenticated RFQ; it does not reserve capacity. Managed inference through Itô is not live yet.