kirkchinese/harness-forge--packages-harness-forge-testkit-lab-plugin ↗★ 6
@kirkchinese/dsh-harness-lab
Test-only DSH plugin used by the Harness Forge conformance runner
Install
npx -p @deepseek-ai/dsh dsh plugin --profile web add 'github:kirkchinese/harness-forge#2e05143dd2407cfb899f46afc6d5fb824bf8b3d6&path:packages/harness-forge/testkit/lab-plugin'README
Read the full README ↗Harness Forge
Bring your Claude Code, Codex and OpenCode plugins and your own settings into DeepSeek Harness. What works is measured in real sessions and every part that does not is listed with the reason; a part DSH lacks can be handed to the AI inside DSH, which writes an adapter in the porting studio, open-sourced when you agree.
中文 · English
0.2.0 is on npm (2026-11-21); 0.1.1 is a deprecated preview. The earlier product of this repository, Claude2DSH (Claude Code session migration), is kept unchanged in
legacy/claude2dsh/; Harness Forge's session migration supersedes it.
What it looks like
Open Harness in the DSH sidebar:
- Overview lists Claude Code, Codex and OpenCode on this machine — your own settings and each plugin — and marks every part works / partly works / needs porting / not supported / error, with the reason;
- Migrate all brings a harness into DSH in one click, or migrate plugins one by one;
- next to a part that needs porting, Port with AI opens a porting session in DSH with the task drafted; you press send.
See the quick start (Chinese).
What carries over
| From the plugin | In DSH |
|---|---|
| Skills | Join the DSH skill catalog under their own names; ${CLAUDE_SKILL_DIR}, ${CLAUDE_PLUGIN_ROOT} and !`command` are expanded on load |
| Slash commands | `/ |
-; $ARGUMENTS, $0, named arguments, !commands and@file` behave as in Claude Code | |
| Agents | DSH presets on the default preset with the agent's own prompt, tool list, model and maxTurns; the model delegates through the agent tool |
| Hooks | Run by one broker: Claude and Codex tool names (Bash, Write, apply_patch, …) map to the DSH tools that do the same work; if, async, asyncRewake, updatedInput, Stop continuation and PermissionRequest work; commands run in Git Bash on Windows |
| MCP servers | Tool names match Claude Code (`mcp__plugin_ |
| ___`); stdio, Streamable HTTP and SSE; OAuth sign-in | |
| Code plugins | Claude Code mods and OpenCode plugins run through a host API compatibility layer |
| Your own settings | Skills, commands, agents, MCP servers, hooks and permission rules of ~/.claude and ~/.codex; a project's .claude/ |
| Sessions | Claude Code, Codex and OpenCode history imports as DSH sessions |
The compatibility inventory is the measure of what works. The conformance runner installs pinned third-party plugins into the same composition as DSH Web, drives real sessions with a scripted model, and judges each part by observable behavior; a part that is only installed is not counted as working. What DSH lacks is listed as a gap, never dropped silently.
Porting studio and adapters
Parts DSH has no equivalent for (claude-hud's status line, for example) are written by the AI inside DSH as adapters: separate DSH plugins that call the original plugin's own code. The studio scaffolds them, checks them (including that no path of the porting machine is baked in), tries them in an isolated profile, and prepares publication, which needs an independent review and the funder's consent. Published adapters live in harness-forge-adapters, which is also a DSH plugin market index.
Install
After the release:
dsh plugin --profile web add @kirkchinese/dsh-claude-suite # Harness Forge + capability catalog + Recollect memory
dsh plugin --profile web add @kirkchinese/dsh-harness-compat # Harness Forge only
From source (Node.js 24, pnpm 11, Git; DSH `>=0.2.1-rc.2 .tgz file:dist/ .tgz dsh web
Migrating runs a plugin's hooks, MCP servers and code with your permissions, as the original harness does; migrate plugins you trust.
## Development
```sh
pnpm typecheck
pnpm test
pnpm corpus # build the lab profile → fetch the corpus → run every sample → write the inventory
| Package | Role |
|---|---|
packages/harness-forge/core | No DSH runtime: scanning per dialect, component model, planning, compatibility assessment, session migration |
packages/harness-forge/plugin | The DSH plugin: install service, runtime bridges, harnessCompat Remote namespace, workbench, porting studio |
packages/harness-forge/testkit | Conformance runner and lab |
packages/harness-forge/suite | Bundle release |
legacy/claude2dsh | The earlier Claude2DSH, kept as a reference; not built or published |
See the docs and development.
License
MIT