oppnc/dsh-kernel-kimi
Kimi Code written in DSH form: the kimi-cli tool surface re-registered as native DeepSeek Harness tools.
项目介绍Project Overview
DSH 插件,把 Kimi Code CLI 的全部工具(ReadFile、WriteFile、Shell、SearchWeb 等共 16 项)以原生 DSH 工具形式接入,名称、参数、行为均与官方一致;并载入上游 system.md 与 kimi-agent、kimi-explore、kimi-plan 三个子代理配方。适用于希望主代理与子代理都跑在 Kimi 内核、复用 Moonshot OAuth 搜索与抓取的场景。需通过 dsh plugin 手动安装并复制 kimi-kernel 预设后启用。
A DSH plugin that ports the Kimi Code CLI tool surface (ReadFile, WriteFile, Shell, SearchWeb, etc., 16 tools total) into native DSH tools with identical names, schemas, and behavior. It also loads the upstream system prompt plus kimi-agent, kimi-explore, and kimi-plan subagent recipes. Use it when you want both the main agent and subagents running on the Kimi kernel with the existing Moonshot OAuth search and fetch endpoints. Install via the dsh plugin command and copy the kimi-kernel preset to activate.
请帮我了解并安装插件:【dsh-kernel-kimi】【https://github.com/oppnc/dsh-kernel-kimi】
把上面这条消息直接发给当前会话里的 DSH,让它帮你了解并安装。安装命令不一定准确,发给 DSH 更稳。Send this message to DSH in your current session. CLI install commands may not be accurate across systems — DSH will figure it out for you.
或使用命令行安装(适合开发者)Or use CLI install (for developers)
命令行安装CLI Install
dsh plugin --profile web add github:oppnc/dsh-kernel-kimi
把 oppnc/dsh-kernel-kimi 加入你的 DSH 配置(web profile)即可启用。
READMEREADME
English | 中文
dsh-kernel-kimi
DSH runs on one simple idea: everything is a plugin. Models, tools, subagents — plug them together however you like.
So we did exactly that: we turned Kimi Code into a DSH plugin. The kimi-cli tool surface you already know — ReadFile, WriteFile, StrReplaceFile, Glob, Grep, Shell, ReadMediaFile, SearchWeb, FetchURL, TaskList, TaskOutput, TaskStop, SetTodoList, AskUserQuestion, Agent, 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.
SearchWeb / 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-cli 1.49.0.
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 github:oppnc/dsh-kernel-kimiThis package is a plain plugin (no
dsh.bundledeclaration), sodsh plugininstalls it as an inactive dependency — that is expected: the preset row below references it by name.Install the
kimi-kernelagent preset: copy its directory into~/.dsh/.agent-presets/kimi-kernel/. The shipped preset already includes thekimi-surfacerow inside the planning group (so the plan tools can reachplanMode); 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.
License
MIT — see LICENSE.
nexu-io/open-design
ruvnet/ruflo
amruthpillai/reactive-resume
esengine/DeepSeek-Reasonix
volcengine/OpenViking
Molunerfinn/PicGo
titanwings/colleague-skill
nocobase/nocobase