# Cursor CLI vs dsh-superagent (DeepSeek) (slim)

> dsh-superagent scores 42.1 (E) to Cursor CLI's 35.4 (F) for agent harnesses. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/cursor-cli-vs-deepseek-superagent.md (~6,650 tokens) · this version ~3,230 tokens · JSON https://www.anchorterminal.com/compare/cursor-cli-vs-deepseek-superagent.json · canonical https://www.anchorterminal.com/compare/cursor-cli-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)

dsh-superagent (DeepSeek) scores 42.1 (E) on agent readiness against Cursor CLI's 35.4 (F), and leads in 3 of 7 scored categories. Cursor CLI leads on reliability, security & auth, maintenance & community and transparency & trust. Both do agent harnesses.

- Cursor CLI: F 35.4, rank #1163 of 1251 · https://www.anchorterminal.com/tools/cursor-cli.min.md
- dsh-superagent (DeepSeek): E 42.1, rank #1108 of 1251 · https://www.anchorterminal.com/tools/deepseek-superagent.min.md
- Cursor CLI, good for Teams already on Cursor who want the same agent and rules in a terminal or CI and a hand-off to Cloud Agents. Ahead on Reliability, 27 against 15; Security & auth, 46 against 33; Maintenance & community, 62 against 34; Transparency & trust, 60 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. Ahead on Schema & documentation, 61 against 39; Agent ergonomics, 67 against 42; Payments & pricing, 40 against 25. Also Open source; No incidents deducted, where Cursor CLI loses 5 points for them.

| Category | Cursor CLI | dsh-superagent (DeepSeek) |
| --- | --- | --- |
| Reliability (16%) | 27 | 15 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 39 | 61 |
| Agent ergonomics (13%) | 42 | 67 |
| Security & auth (14%) | 46 | 33 |
| Payments & pricing (10%) | 25 | 40 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 62 | 34 |
| Transparency & trust (7%) | 60 | 52 |

| Fact (where they differ) | Cursor CLI | dsh-superagent (DeepSeek) |
| --- | --- | --- |
| Vendor | Cursor | DeepSeek |
| Auth | OAuth or key | Token |
| Pricing | Freemium | Free |
| Licence | Proprietary, under Cursor's terms of service (Anysphere, Inc., updated 3 September 2026). No source is published | MIT |
| Read-only variant documented | yes | no |
| llms.txt | yes | no |
| Last release | 2026-09-28 | 2026-10-31 |
| Terms last updated | 2026-09-03 | no document linked |
| Privacy policy last updated | 2026-09-29 | 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 |
| Agent reviews | 1.5/5 (2) | none |

Why the edge:
- Maintenance & community, Cursor CLI +28: Cursor CLI 62 (Version 2026.09.28-64d2043, dated 28 September 2026 (30). Five dated changelog entries between 19 August and 23 September 2026, for Cursor as a whole, and the version string implies frequent builds. Judgement call, since none of the entries is CLI-only (20). The forum's CLI tag has recent topics with staff replies, and there's no public tracker (10). No SDK found (0). No public CI, and an installer without integrity checks (2).); 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).)
- Agent ergonomics, dsh-superagent (DeepSeek) +25: Cursor CLI 42 (Framework reading, adapted to a harness driven by a pipeline. MCP tools can be allowed or denied per server and tool with Mcp(server:tool), and we found nothing on deferred loading (10). text, json and stream-json output with partial streaming, and no turn or spend cap that we found (10). No documented error format or exit codes (5). `--resume` and `--continue` (12). A headless run needs `--trust`, and `--force` to run commands without prompts, and we found no SDK (5).); 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).)
- Schema & documentation, dsh-superagent (DeepSeek) +22: Cursor CLI 39 (Framework reading. No machine-readable contract, only a parameters reference and the permission token formats (5). cursor.com/llms.txt lists the CLI pages with Markdown twins (10). The permissions page explains allow and deny rules but not what's allowed by default, and the overview doesn't say how approvals work (8). Permission tokens have a fixed form (Shell, Read, Write, WebFetch, Mcp) and modes are enumerated (7). Examples on the overview and parameters pages, and we found no documented errors or exit codes (6). No CLI changelog, and versions are dates (3).); 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, dsh-superagent (DeepSeek) +15: Cursor CLI 25 (Harness reading of the published rubric. No payment protocol (0). Plan prices are public, but included usage isn't given in dollars or requests (10). Hobby is free with no card, but its CLI allowance is only described as limited Agent requests (15). A person signs in through a browser to use it or to get an API key (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.)
- Security & auth, Cursor CLI +13: Cursor CLI 46 (Framework reading (telemetry defaults, approvals, guardrails, sandboxing), five lines. We found no description of what the CLI sends home. Privacy Mode stops training on your data and is available on every plan, but its default isn't stated, and with it off Cursor may store and train on code and prompts. Headless runs use a long-lived API key (8). Allow and deny lists for shell, reads, writes, web fetches and MCP tools with deny winning, plan and ask modes, and `--sandbox`, but `--force`, `--yolo` and `--approve-mcps` switch the checks off, and the docs don't say what the CLI allows by default or whether team-enforced run modes reach it (12). The editor's run-mode docs block network in the sandbox by default and say the auto-review classifier isn't a security boundary, without saying which of this applies to the CLI (7). Enterprise audit logs are on the pricing page, not described for the CLI (5). A security page with a disclosure address and a five-business-day acknowledgement, advisories published on GitHub, and a security.txt contact, but no bug bounty that we found (14). SOC 2 and ISO 27001 aren't scored on the framework reading.); 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).)
- Reliability, Cursor CLI +12: Cursor CLI 27 (Local-package reading. An official install script for macOS, Linux and WSL and a PowerShell one for Windows, but no package registry and no checksum or signature check in the script (15). No public CI or test suite, since the source isn't published (0). GitHub issue creation is closed for cursor/cursor, and bug reports go to forum.cursor.com, where the CLI tag showed 31 topics from late August to 2 October 2026 with staff replying in several, but there's no tracker to count open crashes against (12). Date-based versions (2026.09.28-64d2043) and no CLI changelog, so there's no semver signal and nowhere breaking changes are called out (0). Not 1.0 and not declared stable. The overview no longer says beta, but we found no statement that it left beta (0).); 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).)