Head to head · Agent harnesses · October 2026 research run
AXLR vs Emdash
AXLR scores 70.6 (BB) on agent readiness against Emdash's 53.9 (D), and leads in 6 of 7 scored categories. Both do agent harnesses.
Best agent harnesses and coding agents · All 1500 harnesses comparisons
Which one, for what
AXLR BB
Best for A program or bot that needs one governed execution at a time, with a policy, a budget, a sandbox profile and correlation ids it sets itself and a result object it reads back, on a machine it controls, with the model on OpenRouter, a local server or a native Anthropic or OpenAI key.
Ahead on
- Reliability, 70 against 55
- Schema & documentation, 80 against 55
- Agent ergonomics, 83 against 55
- Security & auth, 62 against 38
- Maintenance & community, 79 against 70
Also in its favour
- Agent-ready, a grade of BB or better
- Free to start without a card
Watch for
The setup assistant turns autonomy on and leaves the exec sandbox off, so after setup the model's commands run with the person's rights, bar the destructive list
Emdash D
Best for Developers who want parallel agents in worktrees, fed from their issue tracker, locally or over SSH.
Also in its favour
- No key needed to call it
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.
Agent ergonomics AXLR +28
AXLR 83
Harness reading of the framework line, scored on what a program driving it has to supply. Six local tools plus the host's bookkeeping tools; work modes and an execution policy hide the tools a run may not use, axlr_catalog searches the catalog instead of loading it, forged tools keep the request prefix for the prompt cache, and a context cap of 75,000 prompt tokens opens a successor session (20). local_read, local_search and local_list page with offset, next_offset and max_bytes; StreamEvents takes after, max_events (1 to 256) and wait_ms; a budget per execution in seconds, requests, tool calls and dollars; 32 tool calls a turn and max_session_usd (20). The --exec run ends in one result line with a status, the pending call, every call's outcome and the usage, and exits 0, 3 or 1; service errors carry codes an agent can act on; a budget stop says which limit (budget: requests 20 reached) and leaves the session resumable (16). Idempotency-Key on every turn, approval and direct call with cross-transport replay, expected_revision on decisions, expected_sha256 on worker writes, and an interrupted effectful call left uncertain for an operator rather than retried (19). One command runs a task, but the first launch needs an OpenRouter key or a local server, the service needs a CA, a principals file and remote KMP and MADE before a first session, and the only SDK is the Go library (8). 20+20+16+19+8 = 83.
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).
Schema & documentation AXLR +25
AXLR 80
An OpenAPI 3.1 file for the service (15 paths, 23 schemas, mutualTLS security scheme, additionalProperties: false on request bodies), a checked proto for the gRPC service, and the 19 MCP tools built from the same shared schemas (25). No llms.txt on either site (404), and the docs site renders HTML; the Markdown sources are in the repository (5). The product contract tables what each of the four interfaces can and cannot do, the work-mode table states each mode's purpose and tool policy, the transport parity ledger names every verb's arguments and behaviour, and axlr_tools tells the model to look for a tool before forging one (15). Typed inputs throughout, Idempotency-Key 16 to 128 safe ASCII characters, expected_revision a positive integer, policy levels, sandbox profiles and egress values enumerated, budgets as four integers, and the service rejects unknown fields, invalid types and bodies over 4 MiB (14). Examples in every guide, an error shape of code, message and request_id, named codes (409 idempotency_conflict, 400 invalid_cursor, 422 invalid_policy, invalid_budget, sandbox_unavailable, not_ready, invalid_id), a gRPC status mapping, and the worker's five statuses and three exit codes; no single error reference page (14). /v1 routes and an OpenAPI version of 0.1.0 against a 0.15.0 release, and no changelog beyond the dated notes inside the docs (7). 25+5+15+14+14+7 = 80.
Emdash 55
Harness reading. Docs site and a workspace server package (55).
Security & auth AXLR +24
AXLR 62
Harness reading of the framework checklist, as for the other four harnesses. 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. No product telemetry in the console source (the outbound hosts are openrouter.ai, api.anthropic.com, api.openai.com, a configured local server, api.github.com and github.com for engine downloads, and registry.underpassai.com for the signed catalog index) or in the docs; payload capture is off by default since 9 October 2026, traces omit prompts and credentials, model keys are never given to commands or plugins, and Jev sends requests and answers to TypeSafe only when on, which the setup assistant does when TYPESAFE_API_KEY is set, with a notice on stderr (27). Approval cards, a destructive list that always asks, four work modes, a policy level per execution, a bubblewrap or container sandbox with an enforced egress allow list, and a service that approves nothing but reads. Against that, the setup assistant writes autonomous: true, exec_sandbox is off by default, forged tools run with the person's rights, and the README says the console and worker are not sandboxes (13). Forged tools are refused when a file changes since the forge, a policy forbids calls outside the model, and the docs say MCP tools keep their own side effects, but no prompt-injection guidance was found and MCP results reach the model unmarked (6). The service keeps an event journal, audit records, a receipt with the SHA-256 of every call's arguments and outcome, and correlation ids on every event; the console keeps session records, a redacted app log and /session (14). No SECURITY.md, no security.txt on either host, no advisories, no bug bounty; release checksums and a minisign-signed catalog are integrity, not a programme (2). 27+13+6+14+2 = 62.
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.
Reliability AXLR +15
AXLR 70
Read as a local package, as claude-code, goose, opencode and openhands were. Release archives for Linux, macOS and Windows on amd64 and arm64 with a .sha256 beside each, a GHCR image, an OCI Helm chart and source builds with Go 1.26, all stated in the docs; no Homebrew, npm or apt route (20). CI on main runs vet, race tests and a coverage gate above 80 per cent for both modules, with the sandbox tests required under bubblewrap, and the last ten runs on main to 1 November 2026 all passed; the release workflow tests on six native runners (25). 10 open issues, all opened by the founder on 19 and 21 October 2026 as trackers for service work (work modes, plugins, the sandbox setting, cost limits), none from an outside user and none a crash report, 0 open pull requests and about 100 merged; with 0 stars there is nobody else to report, so the handling of outside reports is untested (20). Tags are semver 0.x and the docs date each behaviour change inline ("until 14 October 2026…"), but the 21 releases have empty notes, there is no CHANGELOG.md, and the product contract records one retirement (the seven 1.0 skill definitions on 5 October 2026) without a notice period (5). Pre-1.0, which the README calls an evolving project (0). 20+25+20+5+0 = 70.
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.
Maintenance & community AXLR +9
AXLR 79
v0.15.0 on 2026-10-25, with commits on main to 2026-11-01 (30). 21 releases between 4 and 25 October 2026 (20). One maintainer (368 of 399 commits, the rest by two agent accounts), 10 open issues that are his own trackers with no comments, about 100 merged pull requests and no outside report to measure a reply against (15). Not in the MCP registry; the Go module and a proto to generate clients from are the only client code, beside the GHCR image and Helm chart (5). Go 1.26 toolchain pinned, release actions pinned by commit SHA, a go-licenses check that the third-party bundle matches the dependency graph, and CI passing on main (9). 30+20+15+5+9 = 79.
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.
Score by category
| Category | Weight this run | AXLR | Emdash | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 70 | 55 | AXLR +15 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 80 | 55 | AXLR +25 |
| Agent ergonomics | 13%16.2 | 83 | 55 | AXLR +28 |
| Security & auth | 14%17.5 | 62 | 38 | AXLR +24 |
| Payments & pricing | 10%12.5 | 60 | 60 | even |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 79 | 70 | AXLR +9 |
| Transparency & trust | 7%8.8 | 55 | 54 | AXLR +1 |
| Negative events | ≤15 | 0 | 0 | |
| Total | BB 70.6/100 | D 53.9/100 |
Facts side by side
| Fact | AXLR | Emdash |
|---|---|---|
| Kind | Agent harness | Agent harness |
| Vendor | Underpass AI | General Action, Inc. |
| Hosted endpoint | no (local only) | no (local only) |
| Transports | ||
| Auth | OAuth or key | None |
| Pricing | Free | Free |
| x402 | no | no |
| Licence | Apache-2.0, with a NOTICE naming Tirso García Ibáñez as the copyright holder | Apache-2.0 |
| Read-only variant documented | no | no |
| llms.txt | no | no |
| Last release | 2026-10-25 | 2026-11-06 |
| Terms last updated | no document linked | no document linked |
| Privacy policy last updated | no document linked | no document linked |
| Popularity | 0 stars | none |
Verdicts
AXLR
A pre-1.0 Go harness with an unusually complete service contract, mutual TLS with principal roles, required idempotency keys, a policy, budget and sandbox per execution, and a result object a program can read. The console's defaults after setup are autonomy on and no sandbox, the project has one maintainer and no outside users yet, and releases carry no notes.
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
AXLR
- Before the first prompt, set
approvals.autonomousto false or run with--approve none, and turnexec_sandbox.modetoautoorrequiredon Linux; after setup both default the other way - Drive a run with
axlr-tui --exec --json --policy <file> --budget <file> --sandbox <file>and read only the lastresultline; exit 3 means a call waits for--decide approve|denywith--session <id> - On the service, send
Idempotency-Key(16 to 128 safe ASCII characters) on every turn, approval and direct call, and pass the session'sexpected_revision; a reused key with a different body answers 409 - A local model must return native tool calls (llama.cpp with
--jinja, vLLM with--enable-auto-tool-choice); setcontext_tokenson the entry andOLLAMA_CONTEXT_LENGTHfor Ollama - Leave
TYPESAFE_API_KEYunset unless you want the setup assistant to switch Jev on, which sends requests and final answers to TypeSafe
Emdash
- Launch with TELEMETRY_ENABLED=false if you don't want telemetry
- Use the SSH mode to keep agents on a remote machine
Questions
Which is better for AI agents, AXLR or Emdash?
AXLR scores 70.6 (BB) on agent readiness against Emdash's 53.9 (D), and leads in 6 of 7 scored categories.
Are AXLR and Emdash open source?
Yes. AXLR is open source (Apache-2.0, with a NOTICE naming Tirso García Ibáñez as the copyright holder). Emdash is open source (Apache-2.0).
Other comparisons with AXLR or Emdash
- Agent Zero vs AXLR
- Agent Zero vs Emdash
- Aider vs AXLR
- Aider vs Emdash
- Amp vs AXLR
- Amp vs Emdash
- Antigravity CLI vs AXLR
- Antigravity CLI vs Emdash
- Auggie CLI vs AXLR
- Auggie CLI vs Emdash
- AXLR vs Claude Code
- AXLR vs Cline
- AXLR vs Conductor
- AXLR vs Crush
- AXLR vs Cursor CLI
- AXLR vs DeepSeek Harness (dsh)
- AXLR vs dsh-superagent (DeepSeek)
- AXLR vs Devin
- AXLR vs Droid CLI
- AXLR vs Pi
- AXLR vs Gemini CLI
- AXLR vs GitHub Copilot CLI
- AXLR vs goose
- AXLR vs Harness²
- AXLR vs HarnessRouter
- AXLR vs Jules
- AXLR vs Junie CLI
- AXLR vs Kilo Code CLI
- AXLR vs Kimi Code CLI
- AXLR vs Kiro CLI
- AXLR vs Letta
- AXLR vs mini-swe-agent
- AXLR vs MiniMax Code
- AXLR vs Mistral Vibe CLI
- AXLR vs Muse Code
- AXLR vs OpenAI Agents API
- AXLR vs OpenAI Codex
- AXLR vs OpenCode
- AXLR vs OpenHands
- AXLR vs OpenMausBot
- AXLR vs Orca
- AXLR vs Paseo
- AXLR vs Prime Agent
- AXLR vs Qoder CLI
- AXLR vs Qwen Code
- AXLR vs Mirror CLI
- AXLR vs Rovo Dev CLI
- AXLR vs Sculptor
- AXLR vs T3 Code
- AXLR vs Traycer
- AXLR vs Unstoppable
- AXLR vs Verdent
- AXLR vs Vibe-Trading
- AXLR vs Warp (Warp Agent CLI and the Oz Agent API)
- Claude Code vs Emdash
- Cline vs Emdash
- Conductor vs Emdash
- Crush vs Emdash
- Cursor CLI vs Emdash
- DeepSeek Harness (dsh) vs Emdash
- dsh-superagent (DeepSeek) vs Emdash
- Devin vs Emdash
- Droid CLI vs Emdash
- Pi vs Emdash
- Emdash vs Gemini CLI
- Emdash vs GitHub Copilot CLI
- Emdash vs goose
- Emdash vs Harness²
- Emdash vs HarnessRouter
- Emdash vs Jules
- Emdash vs Junie CLI
- Emdash vs Kilo Code CLI
- Emdash vs Kimi Code CLI
- Emdash vs Kiro CLI
- Emdash vs Letta
- Emdash vs mini-swe-agent
- Emdash vs MiniMax Code
- Emdash vs Mistral Vibe CLI
- Emdash vs Muse Code
- Emdash vs OpenAI Agents API
- Emdash vs OpenAI Codex
- Emdash vs OpenCode
- Emdash vs OpenHands
- Emdash vs OpenMausBot
- Emdash vs Orca
- Emdash vs Paseo
- Emdash vs Prime Agent
- Emdash vs Qoder CLI
- Emdash vs Qwen Code
- Emdash vs Mirror CLI
- Emdash vs Rovo Dev CLI
- Emdash vs Sculptor
- Emdash vs T3 Code
- Emdash vs Traycer
- Emdash vs Unstoppable
- Emdash vs Verdent
- Emdash vs Vibe-Trading
- Emdash vs Warp (Warp Agent CLI and the Oz Agent API)
- AXLR vs Clawboo
- AXLR vs CLI Manager
- AXLR vs Harness
- AXLR vs Paperclip
- AXLR vs Parallax
- Clawboo vs Emdash
- CLI Manager vs Emdash
- Emdash vs Harness
- Emdash vs Paperclip
- Emdash vs Parallax
Machine-readable
- This page as Markdown
/compare/axlr-vs-emdash.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/axlr.json·/api/v1/tools/emdash.json - From a terminal
anchor compare axlr emdash(the CLI) - Over MCP
compare_tools {"a": "axlr", "b": "emdash"}at/mcp, no key