So we did exactly that: we turned Kimi Code into a DSH plugin. The Kimi Code CLI 0.39.1 tool surface you already know — Read, Write, Edit, Glob, Grep, Bash, ReadMediaFile, WebSearch, FetchURL, TaskList, TaskOutput, TaskStop, WaitFor, TodoList, AskUserQuestion, Skill, Agent, AgentSwarm, CreateGoal, GetGoal, SetGoalBudget, UpdateGoal, CronCreate, CronList, CronDelete, ExitPlanMode, EnterPlanMode — is now a set of native DSH tools. Same names, same schemas, same behavior.

The payoff is simple: use the kimi CLI natively inside DSH — no different from opening Kimi Code itself. Every model stays in the environment it knows best — main agent or subagent, it feels like coming home.

WebSearch / FetchURL talk to the same Moonshot endpoints the Kimi CLI uses (api.kimi.com/coding/v1/search and /fetch) with the shared OAuth token. Distilled from Kimi Code CLI 0.39.1 (@moonshot-ai/kimi-code).

We differentially verified against the real kimi CLI: the same task on the same directory produces identical results, item by item.

System prompt & subagents

lib/system-prompt.js carries the upstream Kimi Code CLI system.md (runtime placeholders adapted to DSH); apply() registers it as the agent's sole system-prompt section (complete: true + suppressRuntimeContext()).

lib/subagents.js ships the kernel's own subagent recipes — kimi-agent (coder), kimi-explore, kimi-plan — each = the full system prompt with the upstream roleAdditional block inserted. The mesh loads them and mounts this plugin on each child with a config.tools whitelist.

Install

Install the plugin into your profile with the official plugin command:
```
dsh plugin --profile web add dsh-kernel-kimi
```
GitHub also works (dsh plugin --profile web add github:oppnc/dsh-kernel-kimi) because lib/ ships in the repository.

This package is a plain plugin (no dsh.bundle declaration), so dsh plugin installs it as an inactive dependency — that is expected: the preset row below references it by name.
The kimi-kernel agent preset ships in dsh-kernel-mesh's presets/ directory. Copy it into the official user-preset root (or, if you run without the mesh, get the preset directory from the mesh repo):
```
dsh_home="${DSH_HOME:-$HOME/.dsh}"
cp -r "$dsh_home/profiles/web/node_modules/dsh-kernel-mesh/presets/kimi-kernel" "$dsh_home/.agent-presets/"
```
The preset already includes the kimi-surface row inside the planning group (so the plan tools can reach planMode); if you author your own preset, add it there:
```
- id: kimi-surface
  name: dsh-kernel-kimi
```

Usage

Start a session on the kimi-kernel preset and pick the model kimi-kernel/k3-256k. Your main agent runs on the Kimi kernel with the full kimi tool surface.