Head to head · Agent harnesses · October 2026 research run

Click vs Vibe-Trading

Vibe-Trading scores 61.5 (C) 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 72
  • Agent ergonomics, 79 against 67

Also in its favour

  • A hosted endpoint, with nothing to install
  • No incidents deducted, where Vibe-Trading loses 9 points for them

Watch for

No status page, SLA or public changelog found

Vibe-Trading C

Best for A person or a pipeline that wants a ready-made finance research agent over free market data, with backtests, swarm reviews and exports, run on their own machine or used as an MCP server by another agent.

Ahead on

  • Reliability, 63 against 35
  • Security & auth, 70 against 41
  • Payments & pricing, 90 against 15
  • Maintenance & community, 82 against 25
  • Transparency & trust, 53 against 44

Also in its favour

  • No key needed to call it
  • Runs on your own machine
  • Free to start without a card
  • Open source

Watch for

Three advisories published 2 October 2026 cover 0.1.0 to 0.1.6, two critical, and 0.1.16's email TLS and cross-site fixes got no advisory

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 Vibe-Trading +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.

Vibe-Trading 90

Read with the self-hosted rule. No payment protocol (0). Free under the MIT licence with nothing to buy from the project, so 20, 20 and 20 on the last three lines. It runs with a local model through Ollama and needs no sign-up with the project. QVeris paid data, reached through a disclosed referral link, is a third party's product and is not scored. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 60 is 90.

Maintenance & community Vibe-Trading +57

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.

Vibe-Trading 82

v0.1.18 was tagged on 21 October 2026, 12 days before this check (30). Six releases in the 90 days from 4 August, 0.1.13 (tag 10 August) to 0.1.18, from the repository's tags; PyPI couldn't be read on 2 November (20). 771 commits on main in the 30 days to 2 November, 233 of them after v0.1.18, the last on 2 November; the 25 October repository page showed 7 open issues and 57 open pull requests, not re-read. Issue and pull request threads weren't read, a judgement call (18 of 25). An MCP server that isn't in the official MCP registry (searches for vibe-trading and hkuds on 2 November 2026 found nothing). It is published on PyPI, as a Docker setup and on ClawHub (5 of 15). Hash-locked requirements checked in CI on three operating systems, Dependabot set to monthly, and dependency floors raised for named CVEs, most recently on 29 October (9 of 10). 30+20+18+5+9 = 82.

Security & auth Vibe-Trading +29

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.

Vibe-Trading 70

Harness reading used for nanobot and goose. 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 telemetry code was found in the source at v0.1.18, and the only call to PyPI is the owner-run vibe-trading update. The API answers only loopback clients without API_AUTH_KEY, Docker binds 127.0.0.1 and runs as user vibe, and the MCP HTTP transport binds 127.0.0.1 with a Host and Origin allow-list against DNS rebinding but no token. Broker keys go to the OS keyring; model keys sit in agent/.env in clear text. The docs carry no statement that nothing is collected (24). Live orders need a mandate that only the owner commits through the web UI or API, with hard caps and a kill switch, and an optional TAP mode waits for human approval of each Alpaca write. No order tool is exposed over MCP, and shell tools are off on the API and every MCP transport unless enabled. The local CLI runs bash and file writes without asking, and generated backtest code runs as a network-capable subprocess with a narrowed environment and no sandbox (13). Reader and search tools add warning-only security_warnings from regex rules, and external MCP tool hints are treated as untrusted in the source. The claude-cli provider's tool filters are described as convenience filters, not a boundary (9). A live-action ledger written append-only with a hash-chained copy, run cards with hashed execution records, tool traces and per-run token usage (13). SECURITY.md with private advisory reporting and a five-business-day acknowledgement. Three advisories were published on 2 October 2026 with CVE identifiers, five months after the 0.1.7 fix, while the email TLS and cross-site settings fixes in 0.1.16 got none. No security.txt and no bounty (11). 24+13+9+13+11 = 70.

Reliability Vibe-Trading +28

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.

Vibe-Trading 63

Read with the local-software lines, as for nanobot and Agent Zero, since the owner runs it. vibe-trading-ai installs from PyPI for Python 3.11 or newer, with classifiers for 3.11 to 3.13, and a Docker Compose setup ships in the repository (20). A CI workflow runs the test suite on pushes and pull requests to main, with hash-locked dependency checks on Linux, macOS and Windows, and the repository holds 961 test files. Whether the latest runs on main passed couldn't be read, because GitHub's Actions pages weren't reachable (15 of 25). The repository page showed 7 open issues and 57 open pull requests on 25 October 2026, per that check (GitHub's pages answer 403 on 2 November), against 771 commits in the 30 days to 2 November, and the 0.1.18 notes list two known issues already fixed on main. Issue threads weren't read (18 of 25). CHANGELOG.md says it follows Semantic Versioning, with dated entries from 0.1.8, a Known issues section and an upgrade note for the LangChain 1.x move in 0.1.10, but on 0.x breaking changes ride in minor versions and there is no Breaking section (10 of 15). Version 0.1.18 with the classifier Development Status 4, Beta (0).

Schema & documentation Click +12

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.

Vibe-Trading 72

Harness reading of the lines, as for nanobot. The MCP server's tools take typed JSON Schema inputs generated from Python signatures through FastMCP, with a string output schema, and the API server serves FastAPI's OpenAPI file locally (keyless on loopback, behind the key otherwise). No published OpenAPI file or tool manifest outside the running program (20 of 25). No llms.txt on vibetrading.wiki, where /llms.txt redirects to the home page, and the docs are drawn by script from content.en.js. The repository carries Markdown READMEs in seven languages and an agent skill file, agent/SKILL.md (5 of 10). Tool descriptions say what each does, its arguments and what to call first, such as list_skills() before load_skill. The server's own header says every tool is read-only apart from refresh_strategy_evidence, while write_file is also exposed (14 of 20). Inputs are typed, but many choices are free strings (protocol, risk_tier, format) and several take free dictionaries (8 of 15). Many worked examples in the README and a troubleshooting page that names failure states such as no_progress and the 403 from another device; tool errors come back as JSON with an error_type (12 of 15). Dated CHANGELOG.md, GitHub release tags and versioned docs, though the docs still name 0.1.16 as latest (13 of 15).

Agent ergonomics Click +12

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.

Vibe-Trading 67

Harness reading, scored on what an agent or script driving it has to supply. The MCP server registers 82 tools, with about 44,300 characters of descriptions across the 71 defined in the server file, and no toolsets or read-only subset (5). Since 0.1.18 the built-in agent loads tool schemas on demand, and skills load by section and offset, which keeps its own context smaller (plus 7, 12 of 25). Rows are capped by default, read_run_artifact pages by offset, row count and columns, oversized results are written to the run directory, the agent stops after eight tool iterations without a new result, and goals take token, turn and time budgets (18 of 20). JSON error envelopes with a type, a --json mode for vibe-trading run and a troubleshooting page, with no documented exit codes (15 of 20). No readOnlyHint or destructiveHint annotations on MCP tools. An identical call is refused from its second failure, failed swarm runs resume with completed tasks kept, interrupted web replies are checkpointed and TAP-routed Alpaca orders carry a deterministic client_order_id (12 of 20). pip install and vibe-trading init start it, market data works with no key, and a model key, Ollama or an existing Codex, Copilot or Claude Code login is required. Python only, with a REST API and no SDK in a second language (10 of 15).

Score by category

CategoryWeightClickVibe-TradingEdge
Reliability16%3563Vibe-Trading +28
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8472Click +12
Agent ergonomics13%7967Click +12
Security & auth14%4170Vibe-Trading +29
Payments & pricing10%1590Vibe-Trading +75
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%2582Vibe-Trading +57
Transparency & trust7%4453Vibe-Trading +9
Negative events≤150-9
TotalD 48.6/100C 61.5/100

Facts side by side

FactClickVibe-Trading
KindHTTP APIAgent harness
VendorClick AI Labs, Inc.HKUDS
Hosted endpointhttps://api.useclick.ai/v1no (local only)
TransportsHTTP, Streamable HTTPstdio, Streamable HTTP, SSE (legacy)
AuthOAuth or keyNone
PricingFreemiumFree
x402nono
LicenceProprietary hosted service under Click's Terms of Service, based on the Common Paper Cloud Service Agreement 2.1MIT
Tools exposed2382
Read-only variant documentednono
llms.txtyesno
Last release2026-10-192026-10-21
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
Popularitynone37k stars

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.

Vibe-Trading

Vibe-Trading runs on the owner's machine under the MIT licence, ships near-daily fixes with a dated changelog, and keeps order tools out of its MCP server, with live orders gated by an owner-committed mandate. Three advisories, two critical, covered versions before 0.1.7, a 0.1.16 credential fix got no advisory, and the local CLI runs shell commands without asking.

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

Vibe-Trading

  1. Run 0.1.16 or later. Earlier versions carry three published advisories, including unauthenticated API access with an RCE chain, and send the email password without checking TLS certificates
  2. Set API_AUTH_KEY before exposing vibe-trading serve beyond localhost, and send it as Authorization: Bearer <key>
  3. Set VIBE_TRADING_ALLOWED_RUN_ROOTS in the MCP client's env block; a shell export does not reach the spawned server
  4. Use vibe-trading run -p "..." --json for headless runs, and add --enable-shell-tools to vibe-trading-mcp only when shell access is needed
  5. Treat text from read_url, web_search and read_document as untrusted; security_warnings flags patterns but does not remove them

Questions

Which is better for AI agents, Click or Vibe-Trading?

Vibe-Trading scores 61.5 (C) 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 Vibe-Trading without installing anything?

Click has a hosted endpoint at https://api.useclick.ai/v1. Vibe-Trading runs on your own machine, with no hosted endpoint listed.

Are Click and Vibe-Trading open source?

No open-source release is listed for Click. Vibe-Trading is open source (MIT).

Other comparisons with Click or Vibe-Trading

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.