dsh-superagent (DeepSeek) vs Harness

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).

Harness 60

v0.4.18_cli and v1.2.89_desktop on 17 October 2026 (30). 548 tags since 9 September 2026 (20). Pull requests numbered past #1,390 merge daily by the team, but issues and outside pull requests could not be read (5). Not in the official MCP registry, which returned nothing for autonomous-ai, although the repository has a server.json. The npm package it names was never published (0). CI workflows for the CLI, desktop, backend and OS, with dependency lockfiles current. Run results unread (5).

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).

Harness 85

Read as an MCP server and CLI. Seven tools with typed JSON Schema inputs, additionalProperties: false and required fields marked, plus --json on every command. No OpenAPI, which a stdio server does not need (23). llms.txt and a Markdown-like agents page written for agents (10). The server instructions and llms.txt say when to use Harness rather than claude -p or codex exec, when to do the work yourself, and never to answer a harness's prompt or ask one to push or deploy (20). An enum on agent, minItems on wait names, minimum and maximum on timeout_seconds and chars. machine, folder and project are free strings (12). Worked examples for parallel runs, handing a task to Codex and waiting, an exit code table, and a Next: line after every answer (13). Per-component semver tags, but the only CHANGELOG.md covers the provider protocol, and we could not read the GitHub release notes (7).

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).

Harness 57

Harness reading of the framework checklist, as for the other harnesses. 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. Product usage counts are on by default, disclosed with an opt-out and without prompts, code or files. Remote traffic is end-to-end encrypted and relays carry ciphertext. Local use needs no account. The daemon updates itself from a checksummed manifest without asking (18). Agents may start harnesses only after the person turns on an account switch that refuses an agent, with four live harnesses at most and closes limited to their own. Against that, installing Harness adds its commands to Claude Code's and Codex's allow rules, Codex runs them outside its sandbox, there is no sandbox of its own, and the device page lists spoken tasks as auto-allowed (13). The instructions tell an agent never to answer a harness's question or permission prompt and never to ask one to publish, deploy, delete or push. Harness output is another agent's text, and no further guidance on it was found (9). Every harness shows in the person's app with who started it, and the device key log keeps an add and remove history. No per-call audit log found (9). SECURITY.md with an email and a three-working-day acknowledgement, and a documented trust model. No security.txt, bug bounty or certification found (8).

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).

Harness 35

Read as local software, since the agents run on the owner's machines. A one-line installer from Autonomous's CDN, DMG and AppImage builds, and App Store and Google Play apps, with macOS and Linux stated as supported and Node managed by the installer. Not on npm or a package registry (20). A public CI workflow runs the CLI suite in four shards, the desktop suite and typechecks, and the vendor's reliability run of 16 September 2026 reports 2,325 CLI, 370 backend and 1,686 desktop tests passing. We could not read CI run results, so credit for the suite only (10). Open issues could not be read, because GitHub's web pages and API were not reachable from our network. Unchecked, so scored absent (0). Tags follow semver per component, but there is no changelog for the app or CLI and breaking changes are not marked in the repository (5). The CLI agents call is 0.4.18 and the npm MCP package is 0.1.0 and unpublished. The desktop app is 1.2.89, but the agent surface is pre-1.0, and Agents can start other agents is an experiment (0). Accounts and the relay are hosted by Autonomous with no status page found.

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).

Harness 82

Seven compact tools, six outside a harness, and server instructions of about 300 words (25). chars sizes a read (4,000 characters by default), all widens the list, and any returns on the first finished harness. No pagination (14). Documented exit codes, refusals returned as answers rather than errors so a model does not retry them, a timed-out wait reported as still working, and Next: on every answer (19). readOnlyHint on whoami, list, wait and read, destructiveHint false on start and send, idempotentHint on close, and a second start of the same name is answered as already starting (16). Two required fields on start, defaults of Claude Code and a 45-second wait. No SDK, but a CLI, an MCP server and a plugin with a skill (8).

dsh-superagent (DeepSeek) 52

MIT, Copyright (c) 2026 DeepSeek Harness Team (30). The prototype has no data statement of its own. DeepSeek Harness's privacy policy (last updated 20 September 2026) names Hangzhou DeepSeek Artificial Intelligence Co., Ltd., says session logs are collected with official model services and may be used to train models with a right to opt out, and says custom model services aren't stored server-side. It agrees with DSH's session-log README, but neither is referred to from the prototype (12). No deprecation policy. The README says the published code differs from DeepSeek's internal version, and docs/006 warns that database migrations are one-way (3). Telemetry and the session-log upload are disclosed with opt-outs in DSH's own reference pages, not in this repository (6).

Harness 64

MIT licence for the whole repository under Autonomous, Inc., with third-party Store covers under their own licences (30). The repository documents what usage counts contain, a 10-day pseudonymous activity mark and the encrypted relay in detail. Autonomous's privacy policy of 7 July 2026 is general to its stores and sites and does not mention Harness (14). The provider protocol promises both revisions side by side for a deprecation window after a breaking change. Nothing similar for the app or CLI (6). Telemetry is disclosed with an opt-out in the app and CLI, but it is on by default and described in the repository rather than in the privacy policy (14).