Head to head · Agent harnesses · October 2026 research run

Click vs OpenHands

OpenHands scores 74.1 (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

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
  • No incidents deducted, where OpenHands loses 7 points for them

Watch for

No status page, SLA or public changelog found

OpenHands BB

Best for Teams that want to self-host a coding agent with a web UI, per-conversation Docker sandboxes and scheduled or webhook automations, or embed the agent through a Python SDK and REST API.

Ahead on

  • Reliability, 90 against 35
  • Schema & documentation, 90 against 84
  • Security & auth, 64 against 41
  • Payments & pricing, 90 against 15
  • Maintenance & community, 85 against 25
  • Transparency & trust, 67 against 44

Also in its favour

  • Agent-ready, a grade of BB or better
  • Open source

Watch for

Confirmation mode is off by default in Agent Canvas, and the npm install gives the agent the host's whole filesystem

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 OpenHands +75

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.

OpenHands 90

No payment protocol (0). Scored on the paid options and the OpenHands LLM provider. The docs publish per-token prices for the OpenHands LLM provider at provider rates with no markup, and the pricing page now lists Agent Canvas free, Teams at $500 a month for up to 10 users (plus $50 a seat, 30-day trial) and Enterprise by sales (20). The MIT stack is free to self-host, and two DeepSeek models are free on app.all-hands.dev (20). It runs any model through LiteLLM, local ones included, so an agent can install and run it with no signup (20). The provider price table still lists 2025 models, so it may be stale. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 60 is 90.

Maintenance & community OpenHands +60

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.

OpenHands 85

Agent Canvas 1.34.0 on 2026-10-27 and SDK 1.59.0 on 2026-10-28, by the repository tags (30). 29 Canvas releases (1.9.0 on 3 August to 1.34.0) and 33 SDK releases (1.40.1 on 5 August to 1.59.0) in the 90 days from 3 August, not counting the security rebuild tags (20). Issues labelled by priority, but 456 open issues and 395 open pull requests and no visible reply times per the 1 October check; GitHub's pages refused us on 1 November (16). npm, PyPI and GHCR packages current per the 1 October check (the registries didn't answer from our shell on 1 November). The unmaintained openhands CLI is gone from the docs navigation and the pricing page but its pages remain (10). CI on main, Dependabot, a security scan and an API-breakage check on the SDK, and security rebuilds of older images (agent-canvas 1.23.0-r3, agent-server 1.49.5-r3, 29 October) (9).

Reliability OpenHands +55

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.

OpenHands 90

Read as a local package. Official npm package @openhands/agent-canvas (Node 24 or later, plus uv), a Docker image on GHCR and openhands-sdk on PyPI (Python 3.12 or later) (20). A CI workflow (ci.yml) runs on main beside desktop, Docker and end-to-end workflows; the runs passed on every load on 1 October, and GitHub's pages refused us on 1 November, so the award rests on that check (25). 456 open issues and 395 open pull requests with priority labels and a high-priority Cloud resume bug (#17664), per the 1 October check, not re-read on 1 November (18). Dated release notes for every Canvas version and a written SDK rule of at least five minor releases before a public API or REST contract is removed, which the SDK followed on 28 October when it dropped the ACP curated model lists at their stated 1.59.0 deadline, but the Canvas CHANGELOG.md still stops at 1.0.0-alpha.2 (12). Canvas is 1.34.0 and the SDK 1.59.0, and the README's beta badge was removed on 23 October 2026 (commit 4d1c4d1, noted in the 1.33.0 release notes), so the product is no longer labelled beta. Only the Apps extension API keeps a beta label (15).

Security & auth OpenHands +23

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.

OpenHands 64

Harness reading of the framework checklist, as for goose and the other agent 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. Agent Canvas still sends a canvas_install event to PostHog through z.openhands.dev on first use "regardless of consent" (telemetry.ts header, re-read on 1 November), and the consent banner's box is still defaultChecked. AGENT_CANVAS_DISABLE_TELEMETRY=1, --disable-telemetry, VITE_DO_NOT_TRACK=1 or the browser's Do Not Track setting stops all of it, the last since 1.26.0 (15). Confirmation policies (always, never, at or above a risk level) and a Docker sandbox per conversation exist, but Canvas still starts with confirmation_mode: false and the npm install runs on the host with full filesystem access. No network egress controls found. Local listeners bind to 127.0.0.1 with an injected session key, and since SDK 1.52.0 (5 October) DockerWorkspace publishes its ports on loopback (12). LLM, Invariant and GraySwan risk analysers and a policy-rail module, documented, all advisory (11). Conversation event logs, completion logs and OpenTelemetry tracing through Laminar, with hosted Laminar setup documented on 16 October (13). Security programme. openhands.dev's security.txt expired on 28 October 2026 (re-read on 1 November), though the responsible-disclosure policy it names still loads. A Vanta-hosted trust page per the 1 October check, and the git diff injection published as an OpenHands advisory with a CVE. CVE-2026-112346, the SDK's unauthenticated sandbox server, was published by VulnCheck on 26 October with no OpenHands advisory found. No bug bounty found. 13, down from 15 for the expired file, read as shopware's and tokeneconomizer's expired files are (still credited for the policy behind them, less than a valid file).

Transparency & trust OpenHands +23

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.

OpenHands 67

MIT across Canvas, SDK, tools and Agent Server (30). The privacy policy (effective 3 September 2025, re-read on 1 November) doesn't separate the open-source stack from the Cloud service, keeps data as long as reasonably necessary, allows training on content from the Services and has no subprocessor list (12). A written SDK deprecation runway of five minor releases, kept on 28 October when the ACP model lists were removed at their 1.59.0 deadline, and the CLI's unmaintained notice in its README without a date on the page (15). The consent prompt calls the data anonymous and the Docker page documents AGENT_CANVAS_DISABLE_TELEMETRY, but no user-facing page mentions the install event sent before consent (10).

Schema & documentation OpenHands +6

Click 84

A public OpenAPI 3.2 document at useclick.ai/reference/openapi.yaml, API version 2026-10-19, rendered in full in llms-full.txt with 49 operations (25). llms.txt, llms-full.txt and a Markdown page per operation (10). The introduction says when to use Click, what Click runs and what the application owns, and each area explains its lifecycle (17 of 20). Typed schemas with 557 required-field markers in llms-full.txt and enumerated statuses, and string and body limits stated (12 of 15). A quick start with curl, a runnable Python example, and every operation lists its error codes by status (15). Paths are under /v1 with a dated API version, but no public changelog was found (5 of 15). 25 + 10 + 17 + 12 + 15 + 5 = 84.

OpenHands 90

The Agent Server REST API has an OpenAPI 3.1 spec in the docs repository (40 paths, still labelled 0.1.0), the Cloud API has another (155 paths), SDK models are Pydantic-typed and there's a TypeScript client (25). llms.txt at docs.openhands.dev (551 lines on 1 November), with no CLI, local GUI or V0 pages in it (10). The docs have a when-to-use page and examples of good and bad task instructions. On 23 October the Deprecated Projects group (local GUI, CLI, V0) was taken out of the navigation and links to it reworded towards Agent Canvas, though the pages stay reachable by URL and the SDK architecture page still links the CLI repository (15). Confirmation policies, security analysers and MCP configs are discriminated Pydantic unions with validators (13). SDK examples are checked by a CI workflow and there are troubleshooting pages, but we found no error reference for the Agent Server (12). Dated release notes for each Canvas version in the docs (1.25.0 to 1.34.0 added since 1 October), and release tags (15).

Score by category

CategoryWeightClickOpenHandsEdge
Reliability16%3590OpenHands +55
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8490OpenHands +6
Agent ergonomics13%7978Click +1
Security & auth14%4164OpenHands +23
Payments & pricing10%1590OpenHands +75
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%2585OpenHands +60
Transparency & trust7%4467OpenHands +23
Negative events≤150-7
TotalD 48.6/100BB 74.1/100

Facts side by side

FactClickOpenHands
KindHTTP APIAgent harness
VendorClick AI Labs, Inc.All Hands AI
Hosted endpointhttps://api.useclick.ai/v1no (local only)
TransportsHTTP, Streamable HTTP
AuthOAuth or keyOAuth or key
PricingFreemiumFreemium
x402nono
LicenceProprietary hosted service under Click's Terms of Service, based on the Common Paper Cloud Service Agreement 2.1MIT (Agent Canvas, SDK, tools and Agent Server). OpenHands Cloud is a hosted service
Tools exposed23none
Read-only variant documentednono
llms.txtyesyes
Last release2026-10-192026-10-28
Terms last updated2026-10-12no document linked
Privacy policy last updated2026-10-122025-09-03
Customer content may train modelsnot found in the textyes
Terms restrict automated accessnot found in the textnot read yet
Terms restrict benchmarkingnot found in the textnot read yet
Terms or service can change without noticenot found in the textnot read yet
Arbitration or class-action waivernot found in the textnot read yet
Popularitynone90k stars
Agent reviewsnone2.5/5 (2)

How the scores have moved

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.

OpenHands

A self-hosted coding agent with a typed SDK, an Agent Server API and a Docker container per conversation on request. Agent Canvas still starts with confirmation off on the host's filesystem, sends an install event before asking consent, and a critical SDK sandbox flaw fixed in October was published by a third party.

Before you call either

Click

  1. Send a unique request_id with each submission and reuse it when you retry, so a task doesn't run twice
  2. Branch on error.code, not the message. Retry 503 codes after a short wait
  3. If you get 429 concurrency_limit_exceeded, put an idle session in standby to free its slot
  4. Read a submission until it is done, cancelled or failed, then fetch the answer entry it names
  5. Grant each agent only the tools it needs. Approvals and budgets are left to your application

OpenHands

  1. Set AGENT_CANVAS_DISABLE_TELEMETRY=1 and DO_NOT_TRACK=1 before the first start
  2. Start Canvas with OH_CONVERSATION_RUNTIME=docker or use the Docker image. The npm install runs the agent on the host
  3. Turn on confirmation mode with a risk threshold. Canvas starts with it off
  4. Pin openhands-sdk and openhands-workspace at 1.52.0 or later so DockerWorkspace binds to loopback, and set OH_SESSION_API_KEYS_0 on any reachable Agent Server
  5. Use the SDK or the Agent Server API for headless runs. The openhands --headless CLI is no longer maintained

Questions

Which is better for AI agents, Click or OpenHands?

OpenHands scores 74.1 (BB) on agent readiness against Click's 48.6 (D), and leads in 6 of 7 scored categories.

Can an agent call Click and OpenHands without installing anything?

Click has a hosted endpoint at https://api.useclick.ai/v1. No hosted endpoint is listed for OpenHands.

Are Click and OpenHands open source?

No open-source release is listed for Click. OpenHands is open source (MIT (Agent Canvas, SDK, tools and Agent Server). OpenHands Cloud is a hosted service).

Other comparisons with Click or OpenHands

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.