Auggie CLI vs dsh-superagent (DeepSeek)

Auggie CLI 43

Local-package reading, as for the other closed-source harnesses. The official npm package with macOS, Linux and WSL stated, but the README asks for Node 22 or later while the docs and the package engines say Node 20, so 2 are held back (18). No public CI or test suite, since the source isn't published. The repository has six workflow files, but it holds docs, examples and issues, not the CLI, and their results couldn't be read (0). The repository's tracker had 93 open and 18 closed issues on 18 October 2026, per our GitHub record, so most reports stay open. Which are crashes or regressions, and how fast maintainers reply, couldn't be read. Every run needs Augment's servers, and the status page records major outages on 1 September 2026 (Cosmos and the CLI unavailable, about 40 minutes) and 9 October 2026 (about five and a half hours across services) (5). A changelog by version with fixes and improvements in sections, dated release notes on the website, and a 1.x guide with a breaking-changes section, though the repository changelog carries no dates (10). The latest 0.x channel is described as the current stable line for production, while 1.x is in preview. Judgement call (10). 18+0+5+10+10 = 43.

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

Auggie CLI 58

Graded on the stable line, as the brief asks. 0.36.0 on 21 August 2026, 58 days before this check (20). The 1.x preview and the 0.37.0 prerelease line had builds on 16 October, with 283 prereleases since 20 July. Judgement call to score the stable line. 0.34.0, 0.35.0 and 0.36.0 between 30 July and 21 August 2026 (20). The public tracker had 93 open and 18 closed issues, and 66 closed and no open pull requests, on 18 October 2026, per our GitHub record. Reply times couldn't be read. A support portal, a subreddit and a dated website changelog (6). TypeScript SDK 0.2.0 of 8 July 2026, and its docs still name older models. The Python SDK's PyPI page answered with a bot check (8). npm builds come from GitHub Actions through trusted publishing with registry signatures, and the changelog records dependency scan fixes. No public CI for the CLI. The repository's six workflow files don't build it, and their results couldn't be read. Its newest GitHub release is v0.28.0 from May 2026, while tags follow npm builds up to 16 October (4). 20+20+6+8+4 = 58.

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

Auggie CLI 20

Harness reading of the published rubric, scored on the Augment subscription the CLI needs. The self-hosted rule doesn't apply. No payment protocol (0). Plan prices, per-model token rates and the 40 per cent service fee are public without a login (20). No free tier was found on the pricing page. The terms mention trials by order (0). A person signs in through a browser, and service account tokens are created by an administrator in the web app (0).

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.

Auggie CLI 47

Framework reading (telemetry defaults, approvals, guardrails, sandboxing), five lines as for the other harnesses. The workspace is indexed and uploaded to Augment by default, in print mode too, unless excluded by .gitignore or .augmentignore. A telemetry endpoint is listed with no description or opt-out found. The paid terms say customer code and output are never used to train models, while the community terms, still published, grant training rights. Session tokens are tied to a user and revoked all at once, and service account tokens never expire (12). Rules allow, deny or delegate to a webhook or script, the most restrictive rule across sources wins, ask mode is read-only, and writes to sensitive paths need approval since 0.34.0. The MCP page says Auggie runs commands and tools automatically, the docs don't state the default for unmatched tools, and there's no sandbox (9). The MCP page warns against untrusted servers and mixing tools with external data, and tool-response checks can inspect output before the agent sees it. No network control was found (6). Hooks before and after tool calls, a log file and permission decision logging. Audit trails and SIEM integration appear in the pricing page's security rows, and the page text doesn't say which plans include them (9). A disclosure address and GitHub private reporting in SECURITY.md, SOC 2 Type II and ISO/IEC 42001 named. No security.txt and no bug bounty found. OSV lists no published advisory for the package and NVD no CVE for Auggie, per our GitHub record, so there's no public advisory record to credit or deduct (11). 12+9+6+9+11 = 47.

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

Auggie CLI 59

Proprietary. The licence is clear on subscription, redistribution and modification, but it says commercial use needs a separate agreement while plans are sold to businesses, and it names Augment Computing, Inc., which sold the CLI to Harness on 8 October (12). The paid terms rule out training on customer code and treat it as confidential. The privacy policy (28 August 2025) gives no retention periods and lists no subprocessors, referring both to a request, and the docs say indexed code is stored by Augment without a retention period (12). The 1.x guide lists breaking changes and retired parts, and the terms promise no materially reduced functionality during an order, but no date for 1.x becoming the default and no notice period were found (8). A telemetry endpoint is disclosed on the network page, with no description of what's sent and no opt-out (3). 12+12+8+3 = 35.

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

Auggie CLI 67

Framework reading. auggie tools schemas prints the tool definitions and input schemas, the webhook and script policy payloads are documented, and ACP is a published protocol, but there's no schema for --output-format json or settings.json (13). docs.augmentcode.com/llms.txt indexes every page with a Markdown twin (10). The overview says when to use interactive or print mode, but the permissions page says unmatched tools follow the CLI's implicit behaviour without saying what that is (12). Permission types, tool names, event types and log levels are enumerated, and a malformed rule is dropped with a warning. The 1.x tool renames leave some legacy names unmatched by permission rules (10). Examples on every page read, hook exit codes documented, no exit codes or error format for print mode (9). Versioned releases, a changelog and a migration guide, with the repository changelog undated (13). 13+10+12+10+9+13 = 67.

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