# Emdash vs Paseo (slim)

> Paseo scores 62.1 (B) to Emdash's 53.9 (D) for agent harnesses. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/emdash-vs-paseo.md (~4,400 tokens) · this version ~1,180 tokens · JSON https://www.anchorterminal.com/compare/emdash-vs-paseo.json · canonical https://www.anchorterminal.com/compare/emdash-vs-paseo
- 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-07
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

Paseo scores 62.1 (B) on agent readiness against Emdash's 53.9 (D), and leads in 5 of 7 scored categories. Emdash leads on reliability. Both do agent harnesses.

- Emdash: D 53.9, rank #933 of 1510 · https://www.anchorterminal.com/tools/emdash.min.md
- Paseo: B 62.1, rank #577 of 1510 · https://www.anchorterminal.com/tools/paseo.min.md
- Emdash, good for Developers who want parallel agents in worktrees, fed from their issue tracker, locally or over SSH. Ahead on Reliability, 55 against 50.
- Paseo, good for Developers who want parallel coding agents on their own machines with no telemetry, reachable from anywhere. Ahead on Schema & documentation, 65 against 55; Agent ergonomics, 70 against 55; Security & auth, 58 against 38; Maintenance & community, 75 against 70; Transparency & trust, 68 against 54.

| Category | Emdash | Paseo |
| --- | --- | --- |
| Reliability (16%) | 55 | 50 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 55 | 65 |
| Agent ergonomics (13%) | 55 | 70 |
| Security & auth (14%) | 38 | 58 |
| Payments & pricing (10%) | 60 | 60 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 70 | 75 |
| Transparency & trust (7%) | 54 | 68 |

| Fact (where they differ) | Emdash | Paseo |
| --- | --- | --- |
| Vendor | General Action, Inc. | Mohamed Boudra |
| Last release | 2026-11-06 | 2026-11-07 |

Why the edge:
- Security & auth, Paseo +20: Emdash 38 (Harness reading. Telemetry is described as optional and disabled in Settings or with TELEMETRY_ENABLED=false, which reads as on by default (15 of 30). Worktree per task and remote machines over SSH (10 of 20). No prompt-injection guidance (5). No audit log (5). No security policy file found (3). 15 + 10 + 5 + 5 + 3 = 38.); Paseo 58 (Harness reading. The README says no telemetry, tracking or forced log-ins (30 of 30). Worktree per agent, on your own machine (10 of 20). No prompt-injection guidance (5). No audit log (5). SECURITY.md (8). 30 + 10 + 5 + 5 + 8 = 58.)
- Agent ergonomics, Paseo +15: 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).); Paseo 70 (Harness reading. A self-hosted daemon that agents can use to create worktrees, launch other agents and talk to them, scriptable from the CLI (70).)
- Transparency & trust, Paseo +14: Emdash 54 (Apache 2.0 (30). A telemetry page on the docs site (not read) (18 of 30). No deprecation policy (5). Disclosed with an opt-out (15 of 20). 30 + 18 + 5 + 15 = 68.); Paseo 68 (Apache 2.0 for everything but third-party components (30). No telemetry and agents run on your machine (22 of 30). CHANGELOG.md, no deprecation policy (10). States no telemetry (20). 30 + 22 + 10 + 20 = 82.)
- Schema & documentation, Paseo +10: Emdash 55 (Harness reading. Docs site and a workspace server package (55).); Paseo 65 (Harness reading. Public docs, a CLI and plugin examples in the repository (65).)
- Reliability, Emdash +5: 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.); Paseo 50 (Local software. Desktop builds, an Android APK, a Docker image and a Nix package (20). ci.yml on the repository; pass state not read (15). GitHub issues and pull requests weren't read (GitHub's pages refuse these sessions), so that line is scored absent (0). CHANGELOG.md (15). Version 0.15.3 (0). 20 + 15 + 0 + 15 + 0 = 50.)
- Maintenance & community, Paseo +5: Emdash 70 (v1.2.11 on 6 November 2026 (30). v1.2.9, v1.2.10 and v1.2.11 within two weeks (20). GitHub issues and pull requests weren't read (GitHub's pages refuse these sessions), so that line is scored absent (0). Current installers and Homebrew cask (15). Release workflows, no test CI (5). 30 + 20 + 0 + 15 + 5 = 70.); Paseo 75 (v0.15.3 and commits on 7 November 2026 (30). More than three releases in 90 days (20). GitHub issues and pull requests weren't read (GitHub's pages refuse these sessions), so that line is scored absent (0). Current builds (15). CI on push (10). 30 + 20 + 0 + 15 + 10 = 75.)