Head to head · Agent harnesses · October 2026 research run
AXLR vs Click
AXLR scores 74.3 (BB) on agent readiness against Click's 48.6 (D), and leads in 6 of 7 scored categories. Both do agent harnesses.
Best agent harnesses and coding agents · All 1767 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 35
- Security & auth, 62 against 41
- Payments & pricing, 90 against 15
- Maintenance & community, 79 against 25
- Transparency & trust, 55 against 44
Also in its favour
- Agent-ready, a grade of BB or better
- Free to start without a card
- Open source
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
Click D
Best for Product teams that want to embed an agent per customer, ticket or document without running the loop, sandbox or browser themselves, with any model.
Also in its favour
- A hosted endpoint, with nothing to install
Watch for
No status page, SLA or public changelog found
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.
Payments & pricing AXLR +75
AXLR 90
No payment protocol (0). Free and Apache-2.0 with nothing to buy, so 20, 20 and 20 on the last three lines by the self-hosted rule, since the docs say what you pay your model provider, the free route needs no card, and it runs local models with no signup at all, the JSON worker without any model. 0+20+20+20 = 60. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 60 is 90.
Click 15
No x402, MPP or L402. The only 402 is card_verification_required (0). Plan prices are public, Free at $0 and Pro at $199 a month with stated allowances, but no per-unit price (15). The Free plan exists, but writes return 402 until a card is verified in the dashboard (0). A person signs up in a browser, verifies a card and creates the key (0). 0 + 15 + 0 + 0 = 15.
Maintenance & community AXLR +54
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.
Click 25
Closed service with no dated changelog. The newest first-hand date is API version 2026-10-19, 30 days before this check, read as within 90 days rather than within 30 since nothing says what shipped then (20). No dated release entries to count (0). Support is by email to the founder, per the terms. No public changelog, issue tracker or community channel was found (5 of 15). No official SDK (0). No public package or CI to check (0). 20 + 0 + 5 + 0 + 0 = 25.
Reliability AXLR +35
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.
Click 35
Hosted lines, for the HTTP API. No status page is linked from the site or the docs (0), so no incident history could be read (5). Concurrent session limits are published per plan (2 on Free, 50 on Pro) with body size limits of 16 MiB, but no request rate limits were found (8 of 15). 429 concurrency_limit_exceeded and the 503 codes are documented, the conventions say to retry 503 after a short wait, and request_id makes submissions safe to retry. No Retry-After header is documented (12 of 15). No SLA in the terms, which leave usage limits to Click's discretion (0). The API carries no beta or preview label (10). 0 + 5 + 8 + 12 + 0 + 10 = 35.
Security & auth AXLR +21
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 catalogue 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 catalogue are integrity, not a programme (2). 27+13+6+14+2 = 62.
Click 41
Platform API keys are revocable, but each has full access to its tenant, including key management. The MCP server's OAuth tokens through WorkOS carry scopes for the MCP endpoint only (20 of 30). Tool grants limit each agent to named tools, and sessions can override grants, but approvals are left to the customer's application and no read-only key was found (8 of 20). Agents read web pages, browser content and MCP results. The docs tell users to keep secrets out of messages and keep MCP tools from returning stored secrets, but give no prompt-injection guidance (3 of 15). Every top-level and nested tool call is recorded and listed per session, and webhook deliveries can be listed (10 of 15). No security.txt (404), disclosure policy or certification found (0). 20 + 8 + 3 + 10 + 0 = 41.
Transparency & trust AXLR +11
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 catalogue 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.
Click 44
Closed service under terms based on the Common Paper Cloud Service Agreement 2.1, dated 12 October 2026, under Delaware law (15 of 30). The privacy statement lists what is collected, names PostHog with session replay for the website and dashboard, and says staff may access service content for support and to improve the service. Retention is "as long as reasonably needed" with no periods. The docs say Click-created sandboxes are deleted with their session (10 of 30). No deprecation policy. The terms promise 30 days' notice of price changes (3 of 20). Providers are described by category, with PostHog the only one named, and processing in the United States and other countries (5 of 20). 15 + 10 + 3 + 5 = 33.
Score by category
| Category | Weight | AXLR | Click | Edge |
|---|---|---|---|---|
| Reliability | 16% | 70 | 35 | AXLR +35 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 80 | 84 | Click +4 |
| Agent ergonomics | 13% | 83 | 79 | AXLR +4 |
| Security & auth | 14% | 62 | 41 | AXLR +21 |
| Payments & pricing | 10% | 90 | 15 | AXLR +75 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 79 | 25 | AXLR +54 |
| Transparency & trust | 7% | 55 | 44 | AXLR +11 |
| Negative events | ≤15 | 0 | 0 | |
| Total | BB 74.3/100 | D 48.6/100 |
Facts side by side
| Fact | AXLR | Click |
|---|---|---|
| Kind | Agent harness | HTTP API |
| Vendor | Underpass AI | Click AI Labs, Inc. |
| Hosted endpoint | no (local only) | https://api.useclick.ai/v1 |
| Transports | HTTP, Streamable HTTP | |
| Auth | OAuth or key | OAuth or key |
| Pricing | Free | Freemium |
| x402 | no | no |
| Licence | Apache-2.0, with a NOTICE naming Tirso García Ibáñez as the copyright holder | Proprietary hosted service under Click's Terms of Service, based on the Common Paper Cloud Service Agreement 2.1 |
| Tools exposed | none | 23 |
| Read-only variant documented | no | no |
| llms.txt | no | yes |
| Last release | 2026-10-25 | 2026-10-19 |
| Terms last updated | no document linked | 2026-10-12 |
| Privacy policy last updated | no document linked | 2026-10-12 |
| Customer content may train models | not read yet | not found in the text |
| Terms restrict automated access | not read yet | not found in the text |
| Terms restrict benchmarking | not read yet | not found in the text |
| Terms or service can change without notice | not read yet | not found in the text |
| Arbitration or class-action waiver | not read yet | not found in the text |
| Popularity | 0 stars | none |
How the scores have moved
Click
No score change since it was listed.
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.
Click
Click's API is described by a public OpenAPI 3.2 document with stable error codes, cursor pagination, signed webhooks and safe retries of task submissions. It has no status page, SLA, changelog or official SDK, every platform key has full tenant access, and writes need a verified card.
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
Click
- Send a unique
request_idwith each submission and reuse it when you retry, so a task doesn't run twice - Branch on
error.code, not the message. Retry 503 codes after a short wait - If you get
429 concurrency_limit_exceeded, put an idle session in standby to free its slot - Read a submission until it is
done,cancelledorfailed, then fetch the answer entry it names - Grant each agent only the tools it needs. Approvals and budgets are left to your application
Questions
Which is better for AI agents, AXLR or Click?
AXLR scores 74.3 (BB) on agent readiness against Click's 48.6 (D), and leads in 6 of 7 scored categories.
Can an agent call AXLR and Click without installing anything?
No hosted endpoint is listed for AXLR. Click has a hosted endpoint at https://api.useclick.ai/v1.
Are AXLR and Click open source?
AXLR is open source (Apache-2.0, with a NOTICE naming Tirso García Ibáñez as the copyright holder). No open-source release is listed for Click.
Other comparisons with AXLR or Click
- Agent Zero vs AXLR
- Agent Zero vs Click
- Aider vs AXLR
- Aider vs Click
- Amp vs AXLR
- Amp vs Click
- Antigravity CLI vs AXLR
- Antigravity CLI vs Click
- Auggie CLI vs AXLR
- Auggie CLI vs Click
- AXLR vs boxes.dev
- 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 Emdash
- AXLR vs Friday
- 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)
- boxes.dev vs Click
- Claude Code vs Click
- Click vs Cline
- Click vs Conductor
- Click vs Crush
- Click vs Cursor CLI
- Click vs DeepSeek Harness (dsh)
- Click vs dsh-superagent (DeepSeek)
- Click vs Devin
- Click vs Droid CLI
- Click vs Pi
- Click vs Emdash
- Click vs Friday
- Click vs Gemini CLI
- Click vs GitHub Copilot CLI
- Click vs goose
- Click vs Harness²
- Click vs HarnessRouter
- Click vs Jules
- Click vs Junie CLI
- Click vs Kilo Code CLI
- Click vs Kimi Code CLI
- Click vs Kiro CLI
- Click vs Letta
- Click vs mini-swe-agent
- Click vs MiniMax Code
- Click vs Mistral Vibe CLI
- Click vs Muse Code
- Click vs OpenAI Agents API
- Click vs OpenAI Codex
- Click vs OpenCode
- Click vs OpenHands
- Click vs OpenMausBot
- Click vs Orca
- Click vs Paseo
- Click vs Prime Agent
- Click vs Qoder CLI
- Click vs Qwen Code
- Click vs Mirror CLI
- Click vs Rovo Dev CLI
- Click vs Sculptor
- Click vs T3 Code
- Click vs Traycer
- Click vs Unstoppable
- Click vs Verdent
- Click vs Vibe-Trading
- Click vs Warp (Warp Agent CLI and the Oz Agent API)
- Agent Relay vs AXLR
- AXLR vs Clawboo
- AXLR vs CLI Manager
- AXLR vs Harness
- AXLR vs herdr
- AXLR vs Paperclip
- AXLR vs Parallax
Machine-readable
- This page as Markdown
/compare/axlr-vs-click-agents.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/axlr.json·/api/v1/tools/click-agents.json - From a terminal
anchor compare axlr click-agents(the CLI) - Over MCP
compare_tools {"a": "axlr", "b": "click-agents"}at/mcp, no key