MIT DSH skill that delegates bounded coding work to a headless CLI executor in an isolated worktree, then reports a structured result, the real diff and an out-of-scope check.
DSH integration
Native runtime
Author-claimed
Safety audit
Unaudited
Last verified
2026-11-12
License
MIT
01What can it help you accomplish?
Hand a bounded coding / refactoring / test-writing subtask to a cheaper headless CLI executor while the host keeps planning and review
A structured `result.json` with the executor summary, real `git diff` patch, changed files, test outcomes, out-of-scope violations and a `needs_human` flag
DSH users who want volume work done by an executor CLI but the diff, acceptance run and integration kept on the host side
Run delegated work in an isolated worktree and review the actual diff instead of the executor's own account
A dedicated `wb-exec/<id8>` worktree with no commit, push or auto-merge, plus `change.patch` and `changed_files_git` taken from the real `git diff`
Teams that need the change reviewed by a human before it lands
02How to install into DeepSeek Harness
Prerequisites
- Python 3.10+ — standard library only, the README states no `pip install` is needed
- One supported CLI executor installed on the same machine: `workbuddy` (default), `codex`, `claude`, `aider`, or `custom` via `WB_CLI` / `WB_CLI_ARGV`
- Git is optional; without it the run degrades to in-place execution and diff capture is unavailable
- On the `workbuddy` backend, an account or plan allowed to use `deepseek-v4.1-flash`
Installation steps
- 01
Install the plugin package with `dsh plugin --profile <profile> add github:Luminousyyh/skill-wb-exec`, or from Plugins → Plugin Market in DSH Desktop
$ dsh plugin --profile <profile> add github:Luminousyyh/skill-wb-exec
- 02
Alternative without the plugin: `git clone` the repo and copy `skills/wb-exec` into your agent's skills directory so the loader finds `<skills-root>/wb-exec/SKILL.md`
$ git clone
- 03
Run `python <SKILL_DIR>/scripts/wb_exec.py doctor` to check CLI, git, environment and state directory
Verify the integration
- `doctor` returns JSON with `ok=true` and the resolved `cli`; when `ok=false` or `cli_error` is non-empty the README says to stop and hand the raw output to the user
03DSH integration and capability boundaries
DSH plugin package whose `ctx.skills` provider publishes `skills/wb-exec/` as a skill the host agent can call
Path whitelist (`owned_paths`)
A task package JSON with `goal`, `context`, `inputs`, `owned_paths`, `acceptance` and `notes`→Changes outside the whitelist are reported in `result.violations` instead of being silently accepted; an empty list means additions only
An empty `owned_paths` is enforced as "new files only", not as "no check"Structured capture and `needs_human` routing
The executor's stream-json output→A machine-readable `result.json` combining a `--json-schema`-constrained result, the git diff, the out-of-scope check and a structured `needs_human` object
`stdout.jsonl` plus `stderr.log` are capped at 64 MiB (`WB_EXEC_LOG_CAP` overrides); crossing the cap kills the child and marks the job failedRecursion guard and path-level dispatch lock
A dispatch call→A `job_id` for a job whose `owned_paths` do not overlap a running one
The child process gets `WB_SUBAGENT=1`, so a nested dispatch is refused with exit code 3; an overlapping dispatch exits 4 with `error: PATHS_LOCKED`Non-blocking supervision commands
`dispatch`, `run`, `status`, `collect`, `cancel`, `jobs`→Background dispatch that returns immediately, heartbeat and timeout visibility, and a read-only `jobs` listing of live claims and recent history
State lives under `~/.wb-exec/` (override with `WB_EXEC_HOME`); `jobs` never prunes or releases a claim
04Who is it for? When not to use it?
Good for
- DSH users who want volume work done by an executor CLI but the diff, acceptance run and integration kept on the host side
- Teams that need the change reviewed by a human before it lands
Not for
- The worktree and `owned_paths` are isolation, not confinement — a process that ignores the boundary is not stopped by it. On the workbuddy backend the child runs with `--permission-mode bypassPermissions`, so the whitelist is what actually constrains the run.
- The default workbuddy backend is hard-coded to DeepSeek V4.1 Flash at effort `max` with no `--model` or `--effort` flag; when the account refuses that model the run fails and the README says not to retry with another model.
- In a non-Git directory the run executes in place, `isolated=false`, no diff is captured, and `owned_paths` becomes the only defence.
- Overlapping `owned_paths` are refused rather than queued: `dispatch` exits 4 with `PATHS_LOCKED`, and the README says to use `jobs` and widen the split instead of clearing the lock file.
- Integration stays on the host: a `pass` in `tests` is not independent verification, and `git commit` / `git push` should only run when the user explicitly asks.
05Compatibility, maintenance and safety notes
- The worktree and `owned_paths` are isolation, not confinement — a process that ignores the boundary is not stopped by it. On the workbuddy backend the child runs with `--permission-mode bypassPermissions`, so the whitelist is what actually constrains the run.
- The default workbuddy backend is hard-coded to DeepSeek V4.1 Flash at effort `max` with no `--model` or `--effort` flag; when the account refuses that model the run fails and the README says not to retry with another model.
- In a non-Git directory the run executes in place, `isolated=false`, no diff is captured, and `owned_paths` becomes the only defence.
- Overlapping `owned_paths` are refused rather than queued: `dispatch` exits 4 with `PATHS_LOCKED`, and the README says to use `jobs` and widen the split instead of clearing the lock file.
- Integration stays on the host: a `pass` in `tests` is not independent verification, and `git commit` / `git push` should only run when the user explicitly asks.
MIT source; every claim here comes from the repository README at the recorded commit, with no independent safety audit.
06Frequently asked questions
How do I install wb-exec into DeepSeek Harness?
Add the plugin package with `dsh plugin --profile <profile> add github:Luminousyyh/skill-wb-exec`, or install it from Plugins → Plugin Market in DSH Desktop. A `ctx.skills` provider then publishes `skills/wb-exec/` as a skill. Without the plugin you can also clone the repo and copy `skills/wb-exec` into your agent's skills directory.
Which executor CLI do I need?
Any one of `workbuddy` (the pinned default), `codex`, `claude`, `aider`, or `custom` through `WB_CLI` plus a `WB_CLI_ARGV` template. It must be installed on the same machine; if it is missing, the plugin installs but `doctor` reports `ok=false` and the skill stops.
Does wb-exec commit or merge the executor's changes?
No. On a Git repository the run happens in a dedicated worktree on a `wb-exec/<id8>` branch with no commit, no push and no auto-merge. Integration is the host's job: `git apply --check` → `git apply` → run the acceptance commands yourself → report.
What stops two jobs from editing the same files?
A path-level dispatch lock: a second dispatch whose `owned_paths` overlap a running job exits 4 with `error: PATHS_LOCKED` and names the holding job, while disjoint paths still run in parallel. `jobs` shows the live claims read-only. A corrupt lock is refused rather than treated as empty.
Can a delegated executor start another wb-exec run?
No. The child process receives `WB_SUBAGENT=1` and the script refuses to dispatch when it sees that variable, exiting with code 3. The README also warns never to call `dispatch` from inside a WorkBuddy / CodeBuddy session, because the child collides with that session's daemon and hangs silently.
07Related DSH workflows
archify
by tt-a1i
Turn any idea, plan, or codebase into a beautiful interactive diagram. An agent skill for Claude Code, Codex, and more.
openviking
by volcengine
Self-evolving Context Database for AI Agents. Unify Agent Memory, Knowledge RAG and Skills.
aitoearn
by yikart
Let's use AI to Earn!
learn-harness-engineering
by walkinglabs
Harness engineering beginner tutorial, from 0 to 1
08Data and sources
`wb-exec` is a **DeepSeek Harness plugin (skill bundle)**: the host agent hands **coding / refactoring / test-writing**…
This repository is a **DSH plugin package** (`package.json` declares `dsh.bundle`). Once installed, a `ctx.skills` provi…
This page is generated from the project’s public documentation, repository metadata and a structured parse of DSH Plugins; last verified on 2026-11-12. Found an error? Submit a correction.
Best DeepSeek Harness Plugins
Twelve plugins worth installing first — picked from the whole catalog, across every category.