DeepSeek Harness (dsh) vs Muse Code

DeepSeek Harness (dsh)

Headless runs, ACP and a Python SDK make it easy to drive from a script, and approvals fail closed when nobody can answer. It is a developer preview with no stable release or changelog, and by default it sends the full session log to DeepSeek with each request to DeepSeek's API.

Muse Code

Muse Code runs with approvals and an OS sandbox on by default, per-host network approval, an append-only event log and a headless mode with documented exit codes. It is the only route to Muse Wonder Full. It is closed source with undated release notes and no free route, and subscriptions allow training on code unless Contributor mode is turned off.

DeepSeek Harness (dsh)

1. Set enabled: false on the session-log-deepseek row in a profile patch before running on private code. Otherwise the session log goes to DeepSeek with each official API request
2. Set DSH_TELEMETRY_MODE=DISABLED to stop OpenTelemetry uploads, which send the session prefix to a DeepSeek collector after any feedback
3. Treat exit code 1 and the turn_end reason as failure. A --json stream can end with a final event for a failed run
4. Run in a disposable container or VM. The sandbox doesn't confine reads or network, and SAFETY.md says the project has had no security audit
5. Pin the version. npm latest (0.2.0-rc.2) and next (0.2.1-rc.2) differ, DeepSeek's changelog asks for 0.2.1-rc.1 or later, and the README warns of breaking changes

Muse Code

1. Set META_API_KEY for headless runs. Browser sign-in isn't available in CI or for Meta Managed Accounts
2. Gate on your own test command, not the exit code. muse exec returns 0 when the turn completes even if tests still fail
3. Pass --max-model-steps on unattended runs so a stuck task can't loop
4. Prefer --disable-approval to --yolo in CI so the sandbox stays on. On Linux the runner needs a working bubblewrap and a non-musl build
5. Turn Contributor mode off in /settings before a subscription session touches private code