English | 中文

dsh-kernel-mesh

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 four coding harnesses — Kimi Code, Grok Build, OpenAI Codex, and MiniMax Mini-Agent — into DSH plugins, bundled in this one package.

The payoff is simple: switch to a Kimi / Grok / Codex / MiniMax model inside DSH, and it's no different from opening each one's own CLI. Every model stays in the environment it knows best — main agent or subagent, it feels like coming home.

What's inside

• L1 kernel routes — kimi-kernel / grok-kernel / codex-kernel / minimax-kernel, registered as DSH model routes your main agent can switch to.
• L2 subagent recipes — kimi-agent / kimi-explore / kimi-plan, grok-agent / grok-explore / grok-plan, codex-agent / codex-explore / codex-worker (each kernel's own subagent types; minimax has none upstream). Each recipe carries the vendor's own subagent prompt and tool whitelist, so a kernel subagent sees and uses exactly what that harness's subagent would — independent of the parent's preset.
• Three kernel tools — kernel_status, kernel_run, kernel_switch.
• Vendor search tools, offered only when opted in — kimi_search / kimi_fetch appear only if dsh-kernel-kimi is installed and a Moonshot credential exists; grok_search / grok_fetch appear only if dsh-kernel-grok is installed and a Grok OAuth credential exists. They stay separate tools (different corpora). Official web_search is DeepSeek's own search and is not a wrapper.

Kernel matrix

System prompts

Each kernel plugin registers the vendor's upstream system prompt (tool names and runtime placeholders adapted to the DSH tool surface) as the agent's sole system-prompt section (complete: true + suppressRuntimeContext()), so a session on a kernel sees ONLY that harness's prompt — not DSH's.

Fallback routes (opt-in)

The vendors have no fallback of their own, so by default each kernel uses its official API. If a kernel's own API is out of quota, set DSH_KERNEL_USE_FALLBACK=1 to route the kernels through your existing subscriptions instead:

Keys are read from ~/.dsh/.credentials.yaml (OLLAMA_API_KEY, MY_OPENCODE_GO_API_KEY). Leave DSH_KERNEL_USE_FALLBACK unset (or 0) for the official kernel APIs.

Install

Install the bundle into your profile with the official plugin command:

dsh plugin --profile web add github:oppnc/dsh-kernel-mesh

dsh plugin forwards to pnpm and reconciles dsh.profile.bundles automatically — this package declares "dsh": { "bundle": { "patch": "./cordis.patch.yml" } }, so it joins the profile's layer stack. Restart the profile afterwards:

dsh web

Usage

kernel_status                          # which kernels, L2 types, transports are registered
kernel_run(kernel, type, task)         # fan a task out to a foreign kernel
kernel_switch('kimi')                  # set the default model route for future sessions

Screenshots

The whole family on GitHub — every README has a one-tap language switch:

<table> <tr> <td><img src="docs/screenshots/01-mesh-readme-en.png" alt="dsh-kernel-mesh README (EN)" width="410"></td> <td><img src="docs/screenshots/02-mesh-readme-zh.png" alt="dsh-kernel-mesh README (中文)" width="410"></td> <td><img src="docs/screenshots/03-kimi-readme.png" alt="dsh-kernel-kimi README" width="410"></td> </tr> <tr> <td><img src="docs/screenshots/04-grok-readme.png" alt="dsh-kernel-grok README" width="410"></td> <td><img src="docs/screenshots/05-codex-readme.png" alt="dsh-kernel-codex README" width="410"></td> <td><img src="docs/screenshots/06-minimax-readme.png" alt="dsh-kernel-minimax README" width="410"></td> </tr> </table>

Full-size images live in [docs/screenshots/](docs/screenshots/).

License

MIT — see [LICENSE](LICENSE).