Head to head · Agent harnesses · October 2026 research run

DeepSeek Harness (dsh) vs Emdash

Emdash scores 53.9 (D) on agent readiness against DeepSeek Harness (dsh)'s 48.5 (D), and leads in 2 of 7 scored categories. DeepSeek Harness (dsh) leads on schema & documentation and agent ergonomics. Both do agent harnesses.

Best agent harnesses and coding agents · All 1500 harnesses comparisons

Which one, for what

DeepSeek Harness (dsh) D

Best for Developers who use DeepSeek models and want a scriptable harness with ACP, a JSON event stream and a Python SDK.

Ahead on

  • Schema & documentation, 77 against 55
  • Agent ergonomics, 68 against 55

Also in its favour

  • Free to start without a card

Watch for

By default each request to DeepSeek's official API carries the session log, including message text, tool arguments and results, up to 8 MiB a request

Emdash D

Best for Developers who want parallel agents in worktrees, fed from their issue tracker, locally or over SSH.

Ahead on

  • Reliability, 55 against 38

Also in its favour

  • No key needed to call it
  • No incidents deducted, where DeepSeek Harness (dsh) loses 8 points for them

Watch for

Telemetry on unless turned off in Settings or with TELEMETRY_ENABLED=false

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Schema & documentation DeepSeek Harness (dsh) +22

DeepSeek Harness (dsh) 77

Framework reading. --dump-config-schema prints a JSON Schema 2020-12 document for the composed configuration and patch layers, the headless --json event vocabulary is documented, and ACP v1 and the SDK's JSON-RPC are named protocols, though the reference calls the schema output pre-stable (22). llms.txt on the docs site, with a raw Markdown address for every page (10). Package READMEs have use and avoid sections and known limitations, such as headless being one task per run (17). Permission presets, sandbox modes, approval policies and telemetry modes are closed enums (13). Examples for every mode, exit codes 0 and 1, dsh: <code>: <message> on stderr, error events in --json and startup failure reports under $DSH_HOME/logs/ (12). Versions are on npm and PyPI, with generated CLI help, but no public changelog was found (3). Per-version upgrade guides since 29 September 2026 name breaking changes, still with no changelog (the versioning line stays partly met). 22 + 10 + 17 + 13 + 12 + 3 = 77.

Emdash 55

Harness reading. Docs site and a workspace server package (55).

Reliability Emdash +17

DeepSeek Harness (dsh) 38

Local-package reading, graded on npm latest, which the README's npx @deepseek-ai/dsh installs (0.2.0-rc.2 per the 18 October check; npm not re-read on 4 November). Official npm package with Node 22.19+ and 24+ stated, and a Python wheel for Python 3.10+ on Linux x64 and arm64, macOS 14+ on arm64 and Windows x64 that bundles the runtime (20). Public CI. ci.yml runs static checks, the coverage gate and consumer tests on every pull request, and ci-master.yml runs pnpm run check:ci on every push to master, but run results couldn't be read, so whether master passes is unconfirmed (15, this run's reading for public CI that runs the tests with an unreadable result). CONTRIBUTING.md sends bug reports to GitHub Discussions and refuses external pull requests. Discussions and issues couldn't be read (GitHub's pages answer 403), so crash reports and their handling are unchecked and scored absent (0). Alpha, next and latest dist-tags separate channels. Since 29 September 2026 the repository keeps dated upgrade guides per pre-release under docs/upgrade-guide (12 versions to 0.2.2-alpha.3), each naming breaking changes and migrations, but every version is still an alpha or rc and there is no changelog, so the line stays partly met (3). Developer preview, no 1.0 or stable release (0). 20 + 15 + 0 + 3 + 0 = 38.

Emdash 55

Local software. Homebrew cask and installers for macOS, Windows and Linux (20). A code-consistency check and release workflows; no test workflow found (10). GitHub issues and pull requests weren't read (GitHub's pages refuse these sessions), so that line is scored absent (0). Stable tags to v1.2.11, release notes on GitHub (10). Version 1.2.11 (15). 20 + 10 + 0 + 10 + 15 = 55.

Agent ergonomics DeepSeek Harness (dsh) +13

DeepSeek Harness (dsh) 68

Harness reading, scored on what a pipeline driving it has to supply. Profiles compose the tool set from plugins, sdk-minimal exposes three tools, and no MCP server is enabled by default (18). Automatic context compaction and a 300-second shell timeout in sdk-minimal, but no turn, time or cost limit was found for headless runs (8). Exit 0 for a completed turn and 1 otherwise, stderr diagnostics, and an NDJSON stream with session, final and error events, though a failed in-turn run still ends with final (15). --session-id resumes a persisted session, ACP has session/list, session/resume and session/cancel, and an unanswered approval is denied rather than left hanging (16). One-argument headless runs, ACP and a Python SDK, and the repository also holds a TypeScript SDK client (@deepseek-ai/dsh-sdk-client) that the Python guide mentions once. Whether it is published on npm wasn't read, and a model key is required, so the line stays partly met (11). 18 + 8 + 15 + 16 + 11 = 68.

Emdash 55

Harness reading. Issue intake from Linear, GitHub, Jira and others, diff review, pull requests and CI checks in one place, local or over SSH (55).

Score by category

CategoryWeight this runDeepSeek Harness (dsh)EmdashEdge
Reliability16%203855Emdash +17
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.27755DeepSeek Harness (dsh) +22
Agent ergonomics13%16.26855DeepSeek Harness (dsh) +13
Security & auth14%17.54038DeepSeek Harness (dsh) +2
Payments & pricing10%12.56060even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.87170DeepSeek Harness (dsh) +1
Transparency & trust7%8.85354Emdash +1
Negative events≤15-80
TotalD 48.5/100D 53.9/100

Facts side by side

FactDeepSeek Harness (dsh)Emdash
KindAgent harnessAgent harness
VendorDeepSeekGeneral Action, Inc.
Hosted endpointno (local only)no (local only)
Transports
AuthAPI keyNone
PricingFreeFree
x402nono
LicenceMITApache-2.0
Read-only variant documentednono
llms.txtyesno
Last release2026-10-172026-11-06
Terms last updatedno document linkedno document linked
Privacy policy last updatedno document linkedno document linked
Popularity245k npm/wknone
Agent reviews3/5 (4)none

How the scores have moved

Verdicts

DeepSeek Harness (dsh)

Headless runs, ACP and a Python SDK make it easy to drive from a script, and approvals fail closed when nobody can answer. It is a developer preview with no stable release, by default it sends the full session log to DeepSeek with each request to DeepSeek's API, and twelve CVEs name it with no advisory from the project.

Emdash

A mature open-source app for parallel coding agents in Git worktrees, with issue intake from a dozen trackers and remote machines over SSH. Telemetry is on unless you turn it off, and no test workflow was found in the repository.

Before you call either

DeepSeek Harness (dsh)

  1. Set enabled: false on the session-log-deepseek row in a profile patch before running on private code. Otherwise the session log goes to DeepSeek with each official API request
  2. Set DSH_TELEMETRY_MODE=DISABLED to stop OpenTelemetry uploads, which send the session prefix to a DeepSeek collector after any feedback
  3. Treat exit code 1 and the turn_end reason as failure. A --json stream can end with a final event for a failed run
  4. Run in a disposable container or VM. The sandbox doesn't confine reads or network, and SAFETY.md says the project has had no security audit
  5. Pin the version. npm latest and next differ, the README warns of breaking changes, and 0.2.2 pre-releases let web_fetch reach private hosts

Emdash

  1. Launch with TELEMETRY_ENABLED=false if you don't want telemetry
  2. Use the SSH mode to keep agents on a remote machine

Questions

Which is better for AI agents, DeepSeek Harness (dsh) or Emdash?

Emdash scores 53.9 (D) on agent readiness against DeepSeek Harness (dsh)'s 48.5 (D), and leads in 2 of 7 scored categories. DeepSeek Harness (dsh) leads on schema & documentation and agent ergonomics.

Are DeepSeek Harness (dsh) and Emdash open source?

Yes. DeepSeek Harness (dsh) is open source (MIT). Emdash is open source (Apache-2.0).

Other comparisons with DeepSeek Harness (dsh) or Emdash

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.