# Cline vs dsh-superagent (DeepSeek) (slim)

> Cline scores 60.5 (C) to dsh-superagent's 42.1 (E) for agent harnesses. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/cline-vs-deepseek-superagent.md (~6,500 tokens) · this version ~3,130 tokens · JSON https://www.anchorterminal.com/compare/cline-vs-deepseek-superagent.json · canonical https://www.anchorterminal.com/compare/cline-vs-deepseek-superagent
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-01
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

Cline scores 60.5 (C) on agent readiness against dsh-superagent (DeepSeek)'s 42.1 (E), and leads in 6 of 7 scored categories. Both do agent harnesses.

- Cline: C 60.5, rank #597 of 1251 · https://www.anchorterminal.com/tools/cline.min.md
- dsh-superagent (DeepSeek): E 42.1, rank #1108 of 1251 · https://www.anchorterminal.com/tools/deepseek-superagent.min.md
- Cline, good for Developers who want an agent inside VS Code or JetBrains that asks before acting and can roll back, with the same engine in a CLI. Ahead on Reliability, 80 against 15; Schema & documentation, 77 against 61; Security & auth, 57 against 33; Payments & pricing, 50 against 40; Maintenance & community, 85 against 34; Transparency & trust, 62 against 52.
- dsh-superagent (DeepSeek), good for Teams on github.com that want a DeepSeek Harness agent to turn allowed people's issue requests into pull requests, run on an isolated machine or OS account. Also No incidents deducted, where Cline loses 8 points for them.

| Category | Cline | dsh-superagent (DeepSeek) |
| --- | --- | --- |
| Reliability (16%) | 80 | 15 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 77 | 61 |
| Agent ergonomics (13%) | 67 | 67 |
| Security & auth (14%) | 57 | 33 |
| Payments & pricing (10%) | 50 | 40 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 85 | 34 |
| Transparency & trust (7%) | 62 | 52 |

| Fact (where they differ) | Cline | dsh-superagent (DeepSeek) |
| --- | --- | --- |
| Vendor | Cline Bot Inc. | DeepSeek |
| Auth | OAuth or key | Token |
| Pricing | Freemium | Free |
| Licence | Apache-2.0 | MIT |
| llms.txt | yes | no |
| Last release | 2026-10-01 | 2026-10-31 |
| Terms last updated | 2025-09-25 | no document linked |
| Privacy policy last updated | 2025-09-24 | 2026-09-20 |
| Customer content may train models | not found in the text | not read yet |
| Terms restrict automated access | yes | not read yet |
| Terms restrict benchmarking | yes | not read yet |
| Terms or service can change without notice | yes | not read yet |
| Arbitration or class-action waiver | yes | not read yet |
| Popularity | 68k stars | none |
| Agent reviews | 2/5 (2) | none |

Why the edge:
- Reliability, Cline +65: Cline 80 (Read as a local package. The `cline` CLI on npm (Node 22 or later), the VS Code extension (VS Code 1.101 or later), a JetBrains plugin and desktop builds (20). The VS Code test workflow passed on every main run we loaded, including the 1 October CLI and SDK releases (25). 645 to 730 open issues and 525 open pull requests, a stale bot that closes issues after 74 quiet days, and open crash reports such as #12493, where aborting a turn can crash the hub daemon (13). The changelog names every version and says when a default model changes, but carries no dates, and 4.0.0 listed its removals (Explain Changes, subagents for a time) under Changed rather than a breaking section (9). Extension 4.1 and CLI 3.0 are past 1.0, while the SDK (0.0.90) and desktop app (0.0.42) aren't (13).); 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).)
- Maintenance & community, Cline +51: Cline 85 (CLI 3.0.68 on 2026-10-01 and extension 4.1.22 on 2026-09-29 (30). 29 extension releases and 34 CLI releases since 2026-07-03 (20). Issues get platform labels, but about 700 open issues and 525 open pull requests sit beside a stale bot, and the newest issue we could see was from 23 July, so we couldn't judge reply times (13). VS Code Marketplace, JetBrains, npm and desktop builds are current, while the SDK packages are 0.0.x (13). CI passes, Dependabot runs, and npm publishing moved to OIDC trusted publishing after the February token compromise (9).); 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).)
- Security & auth, Cline +24: Cline 57 (Harness reading of the framework checklist, used for all five harnesses in this batch. 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 extension sends usage and error events to PostHog unless the user unticks 'Allow error and usage reporting' or turns off VS Code telemetry. The CLI is built with a telemetry key and an enable flag from repository secrets and its reference lists no telemetry setting, so its default is unconfirmed (15). The IDE asks before edits and commands, command auto-approval has been off by default since 4.0.0, and there are per-category Auto Approve toggles, YOLO mode and `CLINE_COMMAND_PERMISSIONS` allow and deny globs. The CLI approves every tool by default outside ACP mode, a command counts as safe when the model marks it so, and there's no sandbox (11). No prompt-injection guidance found in the docs (4). Task history and checkpoints, with OpenTelemetry export and prompt storage for enterprise (12). A valid security.txt (expires 2027-12-31), a Bugcrowd disclosure programme and three advisories published with CVEs, two of which list no patched version (15).); 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).)
- Schema & documentation, Cline +16: Cline 77 (A typed TypeScript SDK with a reference section, a documented one-object-per-line format for `--json`, and an errors page for the Cline API, but no machine-readable spec for the CLI or its config (18). llms.txt at docs.cline.bot, listing a Markdown version of every page (10). Feature pages say when to use each setting, such as the recommended Auto Approve setup (14). `CLINE_COMMAND_PERMISSIONS` takes typed allow and deny globs, and CLI flags are listed with defaults (11). CLI samples, SDK examples and the API errors page (13). A versioned changelog without dates, with dated tags on GitHub (11).); 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).)
- Payments & pricing, Cline +10: Cline 50 (No payment protocol (0). Scored on Cline's paid options. ClinePass is $9.99 a month and Enterprise is contact-sales, and we found no public per-token price list for Cline credits (10). The open-source extension and CLI need no card (20). Your own key, or a local model through Ollama or LM Studio, works with no Cline account (20).); 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.)
- Transparency & trust, Cline +10: Cline 62 (Apache-2.0 (30). The privacy policy at cline.bot/privacy renders only with JavaScript and we couldn't read it. The docs say code stays on the machine apart from model calls and list what telemetry never includes, without retention periods or subprocessors (10). Removals and default-model changes are noted in the changelog, without dates or a written policy (8). The extension's telemetry and its toggle are documented and VS Code's setting is honoured, but the CLI's telemetry isn't documented (12).); 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).)