Head to head · Agent harnesses · October 2026 research run

Click vs Paseo

Paseo scores 65.9 (B) on agent readiness against Click's 48.6 (D), and leads in 5 of 7 scored categories. Click leads on schema & documentation and 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

  • Schema & documentation, 84 against 65
  • Agent ergonomics, 79 against 70

Also in its favour

  • A hosted endpoint, with nothing to install

Watch for

No status page, SLA or public changelog found

Paseo B

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

Ahead on

  • Reliability, 50 against 35
  • Security & auth, 58 against 41
  • Payments & pricing, 90 against 15
  • Maintenance & community, 75 against 25
  • Transparency & trust, 68 against 44

Also in its favour

  • No key needed to call it
  • Open source

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.

Payments & pricing Paseo +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.

Paseo 90

Free self-hosted software with nothing to buy, so 0 for a protocol and 20 each for public pricing, a free tier and onboarding with no sign-up, 60. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 60 is 90.

Maintenance & community Paseo +50

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.

Paseo 75

v0.15.3 and commits on 7 November 2026 (30). More than three releases in 90 days (20). GitHub issues and pull requests weren't read (GitHub's pages refuse these sessions), so that line is scored absent (0). Current builds (15). CI on push (10). 30 + 20 + 0 + 15 + 10 = 75.

Transparency & trust Paseo +24

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.

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.

Schema & documentation Click +19

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.

Paseo 65

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

Security & auth Paseo +17

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.

Paseo 58

Harness reading. The README says no telemetry, tracking or forced log-ins (30 of 30). Worktree per agent, on your own machine (10 of 20). No prompt-injection guidance (5). No audit log (5). SECURITY.md (8). 30 + 10 + 5 + 5 + 8 = 58.

Reliability Paseo +15

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.

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.

Score by category

CategoryWeightClickPaseoEdge
Reliability16%3550Paseo +15
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8465Click +19
Agent ergonomics13%7970Click +9
Security & auth14%4158Paseo +17
Payments & pricing10%1590Paseo +75
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%2575Paseo +50
Transparency & trust7%4468Paseo +24
Negative events≤1500
TotalD 48.6/100B 65.9/100

Facts side by side

FactClickPaseo
KindHTTP APIAgent harness
VendorClick AI Labs, Inc.Mohamed Boudra
Hosted endpointhttps://api.useclick.ai/v1no (local only)
TransportsHTTP, Streamable HTTP
AuthOAuth or keyNone
PricingFreemiumFree
x402nono
LicenceProprietary hosted service under Click's Terms of Service, based on the Common Paper Cloud Service Agreement 2.1Apache-2.0
Tools exposed23none
Read-only variant documentednono
llms.txtyesno
Last release2026-10-192026-11-07
Terms last updated2026-10-12no document linked
Privacy policy last updated2026-10-12no document linked
Customer content may train modelsnot found in the textnot read yet
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

How the scores have moved

Click

No score change since it was listed.

Paseo

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.

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

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

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, Click or Paseo?

Paseo scores 65.9 (B) on agent readiness against Click's 48.6 (D), and leads in 5 of 7 scored categories. Click leads on schema & documentation and agent ergonomics.

Can an agent call Click and Paseo without installing anything?

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

Are Click and Paseo open source?

No open-source release is listed for Click. Paseo is open source (Apache-2.0).

Other comparisons with Click 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.