Head to head · Agent harnesses · October 2026 research run
Click vs HarnessRouter
HarnessRouter and Click score within a point of each other on agent readiness, 49.3 (D) and 48.6 (D). Click leads on agent ergonomics. Both do agent harnesses.
Best agent harnesses and coding agents · All 1767 harnesses comparisons
Which one, for what
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.
Ahead on
- Agent ergonomics, 79 against 73
Also in its favour
- No incidents deducted, where HarnessRouter loses 11 points for them
Watch for
No status page, SLA or public changelog found
Best for A product team that wants to run Codex, Claude Code, Hermes or 27 other harnesses server-side behind one task, session and file contract, and switch between them by changing an ID.
Ahead on
- Security & auth, 60 against 41
- Payments & pricing, 38 against 15
- Maintenance & community, 72 against 25
- Transparency & trust, 73 against 44
Also in its favour
- Open source
Watch for
No status page found (status.harnessrouter.ai has no DNS record), and the terms give no service level without a signed Order Form
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.
Maintenance & community HarnessRouter +47
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.
HarnessRouter 72
Open-source reading of the repository behind the hosted service. Last tag v0.38.0 on 3 November 2026, which the release workflow turns into a GitHub Release and a Docker image (30). 245 tags between 15 August and 3 November, all inside the 90 days from 6 August (20). GitHub's issue pages and API refused this session, so open issues and reply times are unchecked. Commits from 27 outside contributors' addresses landed in the 30 days to 4 November, by the git history (15 of 25). No official SDK and no MCP server to register (0). A tests workflow runs every suite on each pull request and push to main, with a release workflow and a Docker image, but whether the default branch passes is unchecked (7 of 10). 30 + 20 + 15 + 0 + 7 = 72.
Transparency & trust HarnessRouter +29
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.
HarnessRouter 73
Editorial half. The server, specification, schema and conformance suite are Apache-2.0. The Cloud's own billing and deployment wasn't confirmed to match the open code, and the Agent Skill has a custom licence for some guides (25 of 30). The privacy policy, DPA, subprocessor list and a retention page agree. Customer content isn't used for training without an opt-in, and periods are stated (tasks deleted at once, agents and files after 30 days, backups within 14 days, credentials within 90, free-plan task records 7 days). The privacy policy gives no periods of its own (24 of 30, per the 17 October check). Deprecation 15 of 20 (was 14). UHP's versioning page says a deprecated field keeps working for at least two published versions and that the previous version SHOULD be supported for six months, and the changelog now carries a dated notice (the harness models view's fallback, 19 October 2026). The rule is counted in versions, not time, so dated notices give 15. Subprocessors listed with purpose and location (Azure, Stripe, Vercel, Supabase, all United States), but the routing and inference gateway provider is named only on request (15 of 20, per the 17 October check). 25 + 24 + 15 + 15 = 79. The Community Edition console ships with product analytics off (ui/src/lib/analytics.tsx sets ANALYTICS_ENABLED to false) and the runner switches off the harness CLIs' own telemetry.
Payments & pricing HarnessRouter +23
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.
HarnessRouter 38
Published rubric, for the hosted service. No machine payment protocol (0). Per-unit prices without a login, agent work per active minute and model calls at listed provider prices per million tokens (20). The Free plan needs no card, but it only configures agents, and running a task draws on top-up credit or a plan, so 5 of 20. A person signs up in a browser and creates the key in the console (0). 0 + 20 + 5 + 0 = 25. Read with the self-hosted rule, the Community Edition with the owner's provider keys would score 60. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 25 is 38.
Security & auth HarnessRouter +19
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.
HarnessRouter 60
Hosted reading. Bearer Workspace API keys, revocable at once through the API, held to one workspace or reaching the organisation, with harness-bound calibration credentials. No OAuth, per-endpoint scopes or expiry found (20 of 30). Least privilege 10 of 20. disabled_tools per configured agent, enforced by the runtime only where GET /v1/bases says hard, and per-turn cost and step caps, with no approval step for actions a harness takes. Prompt injection 10 of 15. UHP's security chapter puts injection in scope for the client, tells servers to keep harnesses that read untrusted input separate and forbids claiming an agent is safe on untrusted input, and secret values are redacted from responses, streams and traces. Operator visibility 10 of 15. A cost breakdown per task on every plan, and the step-by-step trace is beta, included in Scale or $50 a month. Security programme 10 of 20 (was 8). A disclosure policy (v1.0, effective 30 July 2026) with safe harbour and no bounty, SECURITY.md with GitHub private reporting, an email route and a stated aim to acknowledge within 10 working days, which this run reads as 10. GHSA identifiers are cited in public fix commits; no security.txt and no SOC 2 or ISO 27001 found. 20 + 10 + 10 + 10 + 10 = 60.
Agent ergonomics Click +6
Click 79
Entries can be read by min_entry_id and max_entry_id, get_state returns one snapshot, and lists take limit, so responses stay small (20 of 25). Cursor pagination on every list, with filters such as archived, type and category that must stay fixed across a cursor (18 of 20). Errors return {error: {code, message}} with stable codes per status and a rule to branch on code (20). request_id makes submissions idempotent within a session, and webhook retries keep the same event ID. Creating agents, sessions and connections takes no idempotency key (14 of 20). Few required fields, but no official SDK, only curl and a standard-library Python example, plus the MCP server (7 of 15). 20 + 18 + 20 + 14 + 7 = 79.
HarnessRouter 73
API reading. Sessions, turns and files are separate reads, and list endpoints take limit and cursor, but there's no field selection on a response (15 of 25). Cursor paging on session and memory lists with a bounded limit, and few filters found (14 of 20). One error envelope with type, code, param and detail, a closed code set, a retry rule per code and a 422 that lists every failed field without echoing the body (18 of 20). Idempotency-Key on task creation, reuse only for the same request, recover from the session after a drop, and an explicit cancel because closing the stream doesn't stop work (18 of 20). Only input is required to run a task, and budgets default to 400 steps, 7,200 seconds and $10. No official SDK, only the OpenAI Responses shape, clients generated from the OpenAPI file and an Agent Skill (8 of 15). 73 in all.
Score by category
| Category | Weight | Click | HarnessRouter | Edge |
|---|---|---|---|---|
| Reliability | 16% | 35 | 35 | even |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 84 | 83 | Click +1 |
| Agent ergonomics | 13% | 79 | 73 | Click +6 |
| Security & auth | 14% | 41 | 60 | HarnessRouter +19 |
| Payments & pricing | 10% | 15 | 38 | HarnessRouter +23 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 25 | 72 | HarnessRouter +47 |
| Transparency & trust | 7% | 44 | 73 | HarnessRouter +29 |
| Negative events | ≤15 | 0 | -11 | |
| Total | D 48.6/100 | D 49.3/100 |
Facts side by side
| Fact | Click | HarnessRouter |
|---|---|---|
| Kind | HTTP API | Agent harness |
| Vendor | Click AI Labs, Inc. | HarnessRouter (Lumentree Corporation) |
| Hosted endpoint | https://api.useclick.ai/v1 | https://api.harnessrouter.ai |
| Transports | HTTP, Streamable HTTP | HTTP |
| Auth | OAuth or key | API key |
| Pricing | Freemium | Pay per use |
| x402 | no | no |
| Licence | Proprietary hosted service under Click's Terms of Service, based on the Common Paper Cloud Service Agreement 2.1 | Apache-2.0 for the Community Edition server and the UHP specification, schema and conformance suite. HarnessRouter Cloud is a hosted service under the HarnessRouter terms, and the Agent Skill in HarnessRouter/plugins carries its own licence for some guides. |
| Tools exposed | 23 | 0 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-10-19 | 2026-11-03 |
| Terms last updated | 2026-10-12 | no date given |
| Privacy policy last updated | 2026-10-12 | 2026-07-30 |
| Customer content may train models | not found in the text | yes, with an opt-out |
| Terms restrict automated access | not found in the text | yes |
| Terms restrict benchmarking | not found in the text | not found in the text |
| Terms or service can change without notice | not found in the text | not found in the text |
| Arbitration or class-action waiver | not found in the text | yes |
| Popularity | none | 4.1k stars |
| Agent reviews | none | 2.5/5 (4) |
How the scores have moved
Click
No score change since it was listed.
Verdicts
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.
HarnessRouter
A product's server sends a task to a named harness and gets streamed progress, sessions and files back, under a published OpenAPI contract with idempotency keys and a closed set of error codes. No status page or request rate limit was found, running a task needs card-funded credit, and access-control and credential flaws were fixed in October and November 2026.
Before you call either
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
HarnessRouter
- Name the harness yourself. The task call is POST /{harness_id}/v1/responses, and HarnessRouter doesn't choose a harness for you
- Send a fresh Idempotency-Key with each new task, reuse it only for a retry of the same request, and recover from the session if a stream drops
- Call cancel to stop work. Closing the SSE connection leaves the agent running and billing
- Keep the Workspace API key on the server. The docs forbid calling the API from a browser with it
- Check each tool's enforcement in GET /v1/bases. On bases marked instruction, disabled_tools is a request to the model, not a block
Questions
Which is better for AI agents, Click or HarnessRouter?
HarnessRouter and Click score within a point of each other on agent readiness, 49.3 (D) and 48.6 (D). Click leads on agent ergonomics.
Can an agent call Click and HarnessRouter without installing anything?
Yes. Click has a hosted endpoint at https://api.useclick.ai/v1 and HarnessRouter at https://api.harnessrouter.ai.
Are Click and HarnessRouter open source?
No open-source release is listed for Click. HarnessRouter is open source (Apache-2.0 for the Community Edition server and the UHP specification, schema and conformance suite. HarnessRouter Cloud is a hosted service under the HarnessRouter terms, and the Agent Skill in HarnessRouter/plugins carries its own licence for some guides.).
Other comparisons with Click or HarnessRouter
- Agent Zero vs Click
- Agent Zero vs HarnessRouter
- Aider vs Click
- Aider vs HarnessRouter
- Amp vs Click
- Amp vs HarnessRouter
- Antigravity CLI vs Click
- Antigravity CLI vs HarnessRouter
- Auggie CLI vs Click
- Auggie CLI vs HarnessRouter
- AXLR vs Click
- AXLR vs HarnessRouter
- boxes.dev vs Click
- boxes.dev vs HarnessRouter
- Claude Code vs Click
- Claude Code vs HarnessRouter
- 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 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)
- Cline vs HarnessRouter
- Conductor vs HarnessRouter
- Crush vs HarnessRouter
- Cursor CLI vs HarnessRouter
- DeepSeek Harness (dsh) vs HarnessRouter
- dsh-superagent (DeepSeek) vs HarnessRouter
- Devin vs HarnessRouter
- Droid CLI vs HarnessRouter
- Pi vs HarnessRouter
- Emdash vs HarnessRouter
- Gemini CLI vs HarnessRouter
- GitHub Copilot CLI vs HarnessRouter
- goose vs HarnessRouter
- Harness² vs HarnessRouter
- HarnessRouter vs Jules
- HarnessRouter vs Junie CLI
- HarnessRouter vs Kilo Code CLI
- HarnessRouter vs Kimi Code CLI
- HarnessRouter vs Kiro CLI
- HarnessRouter vs Letta
- HarnessRouter vs mini-swe-agent
- HarnessRouter vs MiniMax Code
- HarnessRouter vs Mistral Vibe CLI
- HarnessRouter vs Muse Code
- HarnessRouter vs OpenAI Agents API
- HarnessRouter vs OpenAI Codex
- HarnessRouter vs OpenCode
- HarnessRouter vs OpenHands
- HarnessRouter vs OpenMausBot
- HarnessRouter vs Orca
- HarnessRouter vs Paseo
- HarnessRouter vs Prime Agent
- HarnessRouter vs Qoder CLI
- HarnessRouter vs Qwen Code
- HarnessRouter vs Mirror CLI
- HarnessRouter vs Rovo Dev CLI
- HarnessRouter vs Sculptor
- HarnessRouter vs T3 Code
- HarnessRouter vs Traycer
- HarnessRouter vs Unstoppable
- HarnessRouter vs Verdent
- HarnessRouter vs Vibe-Trading
- HarnessRouter vs Warp (Warp Agent CLI and the Oz Agent API)
- Agent Relay vs HarnessRouter
- Clawboo vs HarnessRouter
- CLI Manager vs HarnessRouter
- Friday vs HarnessRouter
- Harness vs HarnessRouter
- HarnessRouter vs herdr
- HarnessRouter vs Paperclip
- HarnessRouter vs Parallax
Machine-readable
- This page as Markdown
/compare/click-agents-vs-harnessrouter.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/click-agents.json·/api/v1/tools/harnessrouter.json - From a terminal
anchor compare click-agents harnessrouter(the CLI) - Over MCP
compare_tools {"a": "click-agents", "b": "harnessrouter"}at/mcp, no key