dsh-superagent (DeepSeek) vs Muse Code

dsh-superagent (DeepSeek) 34

Published on 31 October 2026, within 30 days, read as the last published change since no tag or release was found (30). One publication, so not three releases in 90 days (0). Issues, pull requests and Discussions couldn't be read, and the README frames the code as a reference prototype adapted from an internal version (0). No official SDK or registry entry (0). Exact dependency pins and a lockfile, but no CI workflow found, and the docs pin DSH 0.2.1-rc.3 (23 October 2026) while npm latest is 0.2.1-rc.5 (29 October 2026) (4).

Muse Code 75

1.4.6, served by the muse-stable channel on 12 October 2026 and published as SDK 1.4.6 on 11 October (30). The SDK, released in step, published 1.3.0 on 18 September, 1.4.2 on 30 September, 1.4.4 on 8 October and 1.4.6 on 11 October (20). No public tracker for the CLI. The SDK repository takes issues with a written triage guide, and the help centre takes support tickets, neither tested (8 of 25). MIT TypeScript and Python SDKs at 1.4.6, labelled a developer preview (12 of 15). A checksummed launcher and release manifest, but no public CI for the program (5 of 10).

dsh-superagent (DeepSeek) 33

Harness reading of the framework checklist, 30 for what leaves the machine by default, 20 for approvals and sandboxing, 15 for prompt-injection posture, 15 for audit and 20 for the security programme. The superagent profile is created from DSH's Web template, and DSH documents that shipped profiles mount session-log-deepseek, enabled by default, which adds the session log to each official DeepSeek API request, up to 8 MiB. dsh-superagent's docs don't mention it, and its Sessions read issue, pull request and chat text and the repository. Setup and worker shells drop variables named KEY, PASSWORD, SECRET or TOKEN, and GH_TOKEN and GITHUB_TOKEN are removed from git (8). Both presets run danger-full-access without approval as the operator's OS user. docs/006 says the account wrappers don't isolate the process, a worker can run programs by path and read the operator's home directory, and recommends a dedicated OS account. The gate, observe default, blocked commands and no auto-merge as the agent account narrow what it does, not what it can do (6). docs/002 says messages, comments and quoted documents are inputs to a decision and can't change allowed lists, rules or Mandates, bots can never make explicit requests, and prompt edits don't change the gate. Workers with full access still read untrusted Thread text, and no further guidance on that was found (7). Decisions are recorded with reasons, Ticket details show the Trigger, Decision, scope and Policy version, the host records the prompt revisions each Session used, and every GitHub message starts with an automated-agent line by default (12). No SECURITY.md (404 at the root and in .github), no security.txt on www.deepseek.com (404), no bug bounty or advisory found. NVD has no record for the prototype. The CVEs against DSH itself are on the deepseek-harness listing (0).

Muse Code 67

Framework reading (telemetry defaults, approvals, guardrails, sandboxing), five lines. A browser session or a Model API key, cleared by muse logout. Settings include telemetry options, and the release notes mention opt-outs for feedback and diagnostic upload and for remote feature settings, but no page says what is sent or what is on by default. Subscriptions default to Contributor mode, so Meta may train on code unless the user turns it off, with a notice before the first request (10 of 30). Ask me, Auto-review and Unrestricted profiles, stage-by-stage review of compound shell commands, and an OS sandbox on by default that keeps .git, .muse and .agents read-only and refuses to run when it can't confirm containment. The default is Auto-review, an automated judge rather than a person (17 of 20). Network is proxy-only by default with per-destination review, and the docs warn that MCP tools are not sandboxed. The 1.4.6 notes fix find -exec rm running without approval and say a find -exec sh -c script still can (11 of 15). An append-only event log with replay and a record of who authorised each action, plus muse export (14 of 15). Meta's bug bounty, named in the SDK's SECURITY.md, a valid security.txt on www.facebook.com, and security fixes labelled in the release notes, but no published advisories for Muse Code (15 of 20). Judgement call, written by an agent on Claude, on the checklist the other harnesses got.

dsh-superagent (DeepSeek) 15

Local-package reading, since it runs as a DSH bundle on the operator's machine. Not published to npm (private: true in package.json, and the registry has no dsh-superagent). It installs from a git clone with pnpm install && pnpm build on top of @deepseek-ai/dsh@0.2.1-rc.3, with Node 22.19+ or 24+, git 2.32+, Python 3.8+, tmux and gh 2.48+ stated, so half credit (10). A vitest suite of about 25 spec files is listed in docs/007, and pnpm check runs the typecheck, tests and build. Two spec files were read on raw.githubusercontent.com. No CI workflow was found at five common paths under .github/workflows, and the directory couldn't be listed (5). Open issues couldn't be read, because github.com and api.github.com weren't reachable from our network. Unchecked, so scored absent (0). Version 0.1.0 with no tag, release or changelog found, so no semver record (0). A research prototype, not stable (0).

Muse Code 45

Local-package reading. Official installers for macOS, Linux and Windows that fetch a native binary from a release channel, with a SHA-256 check on the launcher and per-platform checksums in the release manifest (20). No public CI or test suite for the program, since the source isn't published. The SDK repository's workflows only publish to npm and PyPI (0). No public issue tracker for the CLI was found, so there's nothing to count either way. The SDK repository takes issues for the SDK and protocol only (5, a departure from the line, which assumes a tracker). Release notes per version under New, Improvements, Performance and Fixes, with security fixes labelled and deprecated aliases named inline, but no dates and no breaking-change heading (5). 1.4.6 (15). Same reading as Claude Code, which is also closed source.

dsh-superagent (DeepSeek) 61

Framework reading, as for deepseek-harness. No OpenAPI or JSON Schema is published. docs/006 documents the Management API's routes, fields, block shapes and refusals in tables, and the code validates settings with zod (12). Markdown docs in the repository, readable raw, and a SETUP.md written for a coding agent. No llms.txt (5). Nine numbered documents read in order, each stating purpose, limits and what not to do, such as never rerunning the profile-creation command for an upgrade (17). Closed sets for accept mode (off, observe, auto), admission cells, Source states, health states and listen (12). A worked curl example, refusals as 400, 404, 409 and 500 with issues, setup or code, a troubleshooting table and status exit codes 0 to 3 (13). package.json says 0.1.0 and pins an engines.dsh range, but no changelog or tags were found (2).

Muse Code 84

Framework reading. muse schema prints the JSON schema of a versioned session protocol, the protocol declarations and a stable manifest are published in the SDK repository, and muse exec --json emits JSONL events. No JSON Schema for settings.json was found (22 of 25). llms.txt at dev.meta.ai/llms.txt with a Markdown copy of each page (10). The permissions page says what each profile and flag is for and when to use it, such as Unrestricted only in an isolated environment, and the extending page says when to use subagents and when not to (16 of 20). Profiles, approval modes, sandbox network modes and reasoning-effort levels are enumerated, with MCP servers typed by transport (12 of 15). Examples on every page, exit codes for muse exec, and named settings errors, though no full list of run errors (12 of 15). A changelog for every version, with no dates (12 of 15).

dsh-superagent (DeepSeek) 40

Self-hosted rule, as for the other open-source harnesses. No payment protocol (0). Free under MIT with nothing to buy (20). No card for the software (20). An agent can't get started alone, because the setup needs a person to create a dedicated GitHub user account, accept the repository invitation and run auth login for the wrappers, which SETUP.md lists as operator steps. 0, as the other harnesses that need an account were read (0). The model provider is a separate purchase.

Muse Code 20

Harness reading of the published rubric. No payment protocol (0). Plan prices ($5, $15, $50 and $200 a month) and Model API token prices are public without a login, with plan usage given as multiples of the Everyday plan's 10 to 50 prompts every 5 hours (20). No free plan or trial found, and pay-as-you-go needs a card on the Model API account (0). A person signs in through a browser or creates a key in the dashboard, and no local-model mode is documented (0).

dsh-superagent (DeepSeek) 67

Harness reading, scored on what a team or pipeline driving it has to supply. The worker preset is DSH's standard with web fetch, plan mode, questions, scheduling and workflows left out, the main Session can't write files, and tool results over 8,192 characters are pruned (18). A concurrency limit with one extra slot for a person's message, a 5-second foreground shell, a 10-minute prepare limit and 30 minutes for background work after a turn. No cost or turn limit per Ticket was found (12). Ticket stages, health entries per part, Reports of blocked or failed, API refusals with codes, and three retries with growing backoff on 408, 429, 5xx and dropped connections (17). Saves carry a revision and a stale one gets 409, state and Sessions survive a restart, and a restarted Assignment gets a recovery note to check git and GitHub before repeating any outside action (16). Sensible defaults (observe mode, port 3082, branch prefix agent/), but setup needs a dedicated GitHub user account, CLI wrappers, tmux and a profile, and there is no SDK. Work is requested by mentioning the agent account on GitHub or Feishu (4).

Muse Code 79

Framework reading, adapted to a harness driven by a pipeline. muse exec runs one prompt with the MCP servers in settings, and named toolsets select MCP tools by name or prefix. We found no deferred tool loading in Muse Code's own docs (18 of 25). --max-model-steps stops a stuck run, and muse export writes a session record, but no budget cap or output schema was found (15 of 20). Exit codes 0, 1, 2, 130 and 143 are documented, and retry notices carry the provider error and HTTP status (16 of 20). --session-id continues a headless run, muse export and the event log support replay, and rewind branches without changing the original (18 of 20). TypeScript and Python SDKs. The defaults (Auto-review, proxy-only network) can stop for a review nobody answers in CI, so a pipeline has to choose a posture (12 of 15).