dsh-superagent (DeepSeek) vs Prime Agent

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

Prime Agent 65

Read with the local-software lines. The vendor's installer fetches checksummed binaries for macOS and Linux on x64 and arm64, with an npm install needing Node.js 20.6 or later as the fallback, but the stable pointer is the TypeScript build while the Rust code on main ships only on the nightly channel, and Windows builds are beta only (17). A public CI workflow runs fmt, clippy with warnings as errors, sharded workspace tests and cargo-deny, and its badge read passing on 8 October 2026 (25). 20 open issues and 91 open pull requests on 8 October. Issues hold only work the maintainers accepted, and the Discussions bug category lists reports from the past two weeks of session-worker crashes, truncated RPC output and provider hangs, whose reply state we did not read (15). Stable releases carry written notes and changes are recorded as fragments in .changes, including the removal of the --tools flags, but there is no changelog file, the nightly notes are boilerplate and the project is at 0.x (8). Version 0.9.8, and the Rust build is a beta (0).

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

Prime Agent 79

Nightly v0.9.9-beta.55 on 7 October 2026 and stable v0.9.8 on 29 September 2026 (30). At least 12 stable tags since 20 August 2026 and 55 nightly betas since 30 September (20). The main branch had at least 200 commits between 22 September and 8 October, and Discussions had new threads daily in October, but issues from unapproved contributors and unsolicited pull requests are closed automatically and we could not read reply times (14). Binaries for five targets from one release workflow and Homebrew definitions in the repository. No SDK and no registry package found (8). A pinned toolchain, a committed lockfile, cargo-deny with two triaged advisory exceptions reviewed on 17 September 2026, and CI passing. An open issue (#3292) reports npm audit findings for the 0.9.8 install, which we did not verify (7).

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.

Prime Agent 60

Self-hosted rule. No payment protocol (0). Free and MIT-licensed with nothing to buy, so 20, 20 and 20 on the last three lines. The model provider is paid separately.

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

Prime Agent 42

Harness reading of the framework line. --mode json emits a session event stream and rpc and acp modes exist, but we found no published schema or reference for them outside the source (10). docs.primeintellect.ai serves an llms.txt that has no Prime Agent page (0). The README states what the agent does, how it differs and that it is not a sandbox, and the bundled skills say when to use each function (10). CLI values are validated with messages that list the valid choices, and MCP tool schemas are read live from the server (7). The README gives the install line and seven commands, and the MCP skill documents its error types, but there is no headless or configuration guide (5). Versioned releases with notes for stable versions, none of substance for nightlies (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).

Prime Agent 50

Harness reading of the framework checklist, as used 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. Usage telemetry is on by default. It is pseudonymous, limited to primitive values with no prompts, tool content or file paths per the source, disclosed on first run and mirrored to a local telemetry.jsonl (18). No approval prompts were found and there is no sandbox, which the README states. MCP tools can be limited with enabledTools and disabledTools, and the agent is told to recommend a connection, not make one (4). The README tells users to work only with trusted repositories, instructions and skills. No detection or mitigation found (5). Append-only JSONL session files, a prime-agent incident timeline command and the local telemetry mirror (12). The vendor's security policy has a reporting address, safe harbour, response times and discretionary rewards, scoped to its website and API. The repository has no SECURITY.md and no published advisories, CONTRIBUTING.md says to report privately without naming an address, and security.txt returned 404. cargo-deny runs in CI (11).

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

Prime Agent 67

MIT in the LICENSE file and Cargo.toml, with a notice that the code is a port of a TypeScript product originally copyright Mario Zechner (30). The first-run notice and the telemetry crate README say what is sent and what is excluded, and name the endpoint and PostHog, but the vendor privacy policy is dated 23 February 2024, does not describe agent telemetry and gives no retention period for it (12). No deprecation policy found. Removed flags are recorded in change fragments (5). Telemetry is disclosed with a setting, a command and two environment variables to turn it off (20).