Head to head · Agent harnesses · October 2026 research run

AXLR vs Paseo

AXLR scores 70.6 (BB) on agent readiness against Paseo's 62.1 (B), and leads in 5 of 7 scored categories. Paseo leads on transparency & trust. 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 50
  • Schema & documentation, 80 against 65
  • Agent ergonomics, 83 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

Paseo B

Best for Developers who want parallel coding agents on their own machines with no telemetry, reachable from anywhere.

Ahead on

  • Transparency & trust, 68 against 55

Also in its favour

  • No key needed to call it

Watch for

Pre-1.0, at 0.15.3

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.

Reliability AXLR +20

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.

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.

Schema & documentation AXLR +15

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.

Paseo 65

Harness reading. Public docs, a CLI and plugin examples in the repository (65).

Agent ergonomics AXLR +13

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.

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 +13

AXLR 55

Apache-2.0 with a NOTICE (30). No privacy policy or terms on underpassai.com or axlr.underpassai.com; the docs' 'Where data goes' and 'Diagnostics and privacy' sections say that model requests go to OpenRouter, the local server or the native API, that Jev sends text to TypeSafe only when on, that sessions live under $XDG_STATE_HOME/axlr, that payload capture is off by default and redacted when on, and that traces are deleted after 30 days; nothing covers the engine downloads' or the catalog registry's handling of a client's requests (15). No deprecation policy; pre-1.0 changes are dated inline in the docs and the product contract records the 5 October 2026 retirement of the first skill catalogue after the fact (6). No telemetry to disclose, and the docs say in two places what leaves the machine and how to stop payload capture, though no single page says there is no telemetry (17). 30+15+6+17 = 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.

Score by category

CategoryWeight this runAXLRPaseoEdge
Reliability16%207050AXLR +20
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.28065AXLR +15
Agent ergonomics13%16.28370AXLR +13
Security & auth14%17.56258AXLR +4
Payments & pricing10%12.56060even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.87975AXLR +4
Transparency & trust7%8.85568Paseo +13
Negative events≤1500
TotalBB 70.6/100B 62.1/100

Facts side by side

FactAXLRPaseo
KindAgent harnessAgent harness
VendorUnderpass AIMohamed Boudra
Hosted endpointno (local only)no (local only)
Transports
AuthOAuth or keyNone
PricingFreeFree
x402nono
LicenceApache-2.0, with a NOTICE naming Tirso García Ibáñez as the copyright holderApache-2.0
Read-only variant documentednono
llms.txtnono
Last release2026-10-252026-11-07
Terms last updatedno document linkedno document linked
Privacy policy last updatedno document linkedno document linked
Popularity0 starsnone

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.

Paseo

A self-hosted, open-source workspace for running many coding agents on your own machines, scriptable from the CLI and reachable from phone, web or desktop, with no telemetry or forced log-in. It's pre-1.0 and run largely by one maintainer.

Before you call either

AXLR

  1. Before the first prompt, set approvals.autonomous to false or run with --approve none, and turn exec_sandbox.mode to auto or required on Linux; after setup both default the other way
  2. Drive a run with axlr-tui --exec --json --policy <file> --budget <file> --sandbox <file> and read only the last result line; exit 3 means a call waits for --decide approve|deny with --session <id>
  3. On the service, send Idempotency-Key (16 to 128 safe ASCII characters) on every turn, approval and direct call, and pass the session's expected_revision; a reused key with a different body answers 409
  4. A local model must return native tool calls (llama.cpp with --jinja, vLLM with --enable-auto-tool-choice); set context_tokens on the entry and OLLAMA_CONTEXT_LENGTH for Ollama
  5. Leave TYPESAFE_API_KEY unset unless you want the setup assistant to switch Jev on, which sends requests and final answers to TypeSafe

Paseo

  1. Run the daemon on the machine that has your tools and credentials, and connect from the clients
  2. Script runs from the CLI for repeatable agent jobs

Questions

Which is better for AI agents, AXLR or Paseo?

AXLR scores 70.6 (BB) on agent readiness against Paseo's 62.1 (B), and leads in 5 of 7 scored categories. Paseo leads on transparency & trust.

Are AXLR and Paseo open source?

Yes. AXLR is open source (Apache-2.0, with a NOTICE naming Tirso García Ibáñez as the copyright holder). Paseo is open source (Apache-2.0).

Other comparisons with AXLR or Paseo

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.