Configuring mstar-harness
DeepSeek Harness loads the portable Agent Plugins v1.0.0 package from the repository root through plugin.json and skills/. The dsh setup described by the README uses the @mstar-harness/dsh adapter and can also install dsh-llm-fallbacks independently. The optional engine CLI is installed globally as @mstar-harness/cli; its canonical executable is mstar-harness, with mstar as a short alias.
The documented workflow setting is:
| Key |
Effect |
enforcement: hard |
Makes dispatch preflights fail fast instead of leaving engine checks advisory |
This setting belongs in an iteration compass. The README does not specify a default value for enforcement.
mstar-harness Commands
The CLI exposes workflow validation commands cited by the skills, including mstar status validate, mstar dispatch validate and mstar iteration gate. Use mstar-harness instead of mstar when the shared executable name is ambiguous. npx @mstar-harness/cli doctor --target <opencode|cursor|codex|zcode|omp|dsh> checks a host setup, while npx @mstar-harness/cli plugin validate validates the portable package.
Workflow entry points include /iteration-start [direction] [pause], /iteration-drive, /iteration-loop [direction] [scale], and /codebase-audit [keywords]. scale accepts S, M, L or XL, defaulting to M; audit effort accepts quick or deep, with standard as the default. Audit output is read-only and goes to {PLAN_DIR}/audit-<date>/.
How mstar-harness behaves
DeepSeek Harness can enter the project-manager workflow through the pm skill, which is not auto-loaded on dsh. The iteration flow covers Phase 1 through Phase 5, either interactively or autonomously. The engine enforces deterministic gates, while mstar-* skills remain the source of role and workflow judgement. Supported host adapters listed by the README are dsh, omp, OpenCode, Cursor, Kimi Code, ZCode and Codex.
mstar-harness limitations and access
The engine checks require @mstar-harness/cli on PATH to run; without it, the harness still works but those checks are advisory unless hard enforcement is configured. The package has an installation-script risk and a terminal surface: setup and CLI operations can install components and run commands with the agent’s available permissions. The mstar alias shares its npm bin namespace with an unrelated package, and co-installation can overwrite the shim.
Written from the project's own documentation and kept in sync with it. Where the two disagree, the source is authoritative — read the README on GitHub