@enderfga/dsh-clawo

A DeepSeek Harness bundle that registers Claw Orchestrator as an ACP subagent provider.

dsh already ships subagent-claude-code and subagent-codex, so delegating to a single coding CLI is covered. This delegates to something none of those can be: a multi-engine runtime. A clawo subagent can answer with one engine, or convene a council of several in isolated git worktrees and hand back the synthesis.

Install

dsh plugin --profile <name> add @enderfga/dsh-clawo

That is the whole setup. The bundle contains no code — it is nine lines of YAML that point dsh's own ACP client at npx @enderfga/claw-orchestrator acp.

Verify it composed into your profile:

dsh --profile <name> --dump-config | grep -A6 subagent-clawo

What the subagent can do

The provider is registered as clawo. Its prompts run through Claw Orchestrator's ACP agent, which supports:

Modes are selected with a slash command in the prompt — /council fix the failing test.

Requirements

• dsh 0.1.0-rc.6 or newer (the dsh.bundle.patch manifest contract and @deepseek-ai/dsh-subagent-acp).
• Node 22.19+ / 24+, matching dsh's own floor.
• Whichever coding CLIs you want Claw Orchestrator to drive, authenticated on the host — claude, codex, and so on. The subagent runs on your machine, not in dsh.

Known limitations

Inherited from the ACP agent, and worth knowing before you rely on them:

• No conversation resume. loadSession is advertised as false. This suits dsh, whose ACP subagent provider starts a fresh session per run and inherits no parent context anyway.
• No mid-turn permission prompt. Claw Orchestrator resolves permission into engine CLI flags when a session opens, so session/request_permission is not implemented. dsh's provider defaults to auto-rejecting permission requests, so nothing is lost here.
• Council is slow. A measured two-round run took roughly nine minutes. It is a deliberate action, not a default.

Why npx and not a dependency

Claw Orchestrator depends on re2, a 17 MB native module used for ReDoS-safe pattern matching. Declaring it as a dependency would make every dsh profile compile a native addon at install time. Fetching the published binary through npx keeps this bundle at three files and zero dependencies, and keeps a failed native build out of your profile install.

Status

dsh is in developer preview and states that compatibility-breaking changes are expected. This bundle depends on exactly two things — the dsh.bundle.patch manifest contract and the config keys of @deepseek-ai/dsh-subagent-acp — so a break here is a YAML fix, not a rewrite. Please open an issue if a dsh release moves either.

License

MIT