kimi

Kimi Code reads the project AGENTS.md from the filesystem natively, and also reads a user-scope AGENTS.md at ~/.kimi-code/AGENTS.md. So agedum leaves the project instructions in place and binds only the global ones. Skills, both scopes, are injected as binds like Claude's.

Wrapper resolution

Project instructions — Kimi Code merges every AGENTS.md from the project root (the nearest .git) down to the working directory into its system prompt (KIMI_AGENTS_MD). The agent-neutral source's AGENTS.md already sits at the project root, which is exactly where Kimi looks, so agedum injects nothing for it — and never tries to, since that root AGENTS.md is typically git-tracked.

Global instructions — Kimi Code also reads a user-scope AGENTS.md at ~/.kimi-code/AGENTS.md, so the global AGENTS.md (base merged with an optional AGENTS.kimi.md overlay) is bound there:

Source	Injected at
global ~/.config/agents/AGENTS.md	~/.kimi-code/AGENTS.md

Both scopes merge natively into KIMI_AGENTS_MD — the project AGENTS.md by tree discovery, the global one from the user-scope path — so agedum appends no flag for instructions. A project with no global scope needs no injection at all: its AGENTS.md is read natively. This mirrors the Claude harness — each scope kept distinct, never merged.

Skills — bound into the directories Kimi Code reads automatically:

Source	Injected at
global ~/.config/agents/skills/	~/.kimi-code/skills/
project .agents/skills/	<root>/.kimi-code/skills/

• Skills use the SKILL.kimi.md overlay where present; assets are copied verbatim.
• The AGENTS.md and skills binds land at paths Kimi Code already reads, so there is no config rewrite and extra_args stays empty.

agedum --wrapper kimi -- kimi -p "explain this code"

Provider config

Kimi Code reads its API token from the environment, so the key goes in requiredEnv (or secretEnv, which is appended automatically) and is exported into the child unchanged. The config knobs become appended CLI flags on the launched command:

{
  "harness": "kimi",
  "slug": "kimi",
  "secretEnv": "MOONSHOT_API_KEY",
  "requiredEnv": ["MOONSHOT_API_KEY"],
  "config": { "model": "kimi-k2", "yolo": true }
}

config key	Appended
model	--model <model>
plan	--plan (true)
yolo	--yolo (true)
binary	overrides the launched CLI name (default kimi)

The config above launches kimi --model kimi-k2 --yolo, with MOONSHOT_API_KEY in the environment. --run seeds a one-shot task with --prompt "<text>" (Kimi Code's --prompt runs once and exits) — it drops --yolo/--plan, which Kimi Code refuses to combine with --prompt. --prompt (seed-then-stay interactive) is unsupported and fails loudly — see the prompt-seeding table.

Kimi Code dropped the --thinking / --no-thinking flags; thinking is now a config setting, so it is applied only through the generated config.toml below (which needs baseUrl).

Custom endpoint — baseUrl

Kimi Code has no base-URL flag, its config does not interpolate $ENV (so a key can't be referenced by name the way pi's models.json does), and there is no --config-file flag. To run Kimi Code against an arbitrary OpenAI-/Anthropic-compatible endpoint, set baseUrl: agedum then generates a config.toml with one provider (named agedum) and one model, bakes the resolved key into it (masked in --dry-run, like opencode's OPENCODE_CONFIG_CONTENT), and binds it over ~/.kimi-code/config.toml — the file Kimi reads from its data dir. Because the bind replaces that file inside the namespace, the generated doc is self-sufficient; Kimi fills every other setting from its own defaults.

{
  "harness": "kimi",
  "secretEnv": "OPENCODE_GO_API_KEY",
  "config": {
    "baseUrl": "https://opencode.ai/zen/go/v1",
    "providerType": "openai",
    "model": "kimi-k2.7-code",
    "contextWindow": 262144,
    "thinking": true
  }
}

config key	Generated config.toml field	Default
baseUrl	providers.agedum.base_url (turns this mode on)	—
providerType	providers.agedum.type	openai
model	models.<model>.model + default_model (required)	—
contextWindow	models.<model>.max_context_size	262144
capabilities	models.<model>.capabilities	["thinking"]
thinking	[thinking].enabled (only when set)	—
(secretEnv value)	providers.agedum.api_key (resolved key, baked in)	—

The above launches kimi --model kimi-k2.7-code, reading the generated ~/.kimi-code/config.toml. baseUrl requires model + secretEnv. providerType must name a Kimi Code provider type (openai for an OpenAI Chat Completions surface, anthropic, kimi, google-genai, openai_responses, vertexai).