Head to head · Agent harnesses · October 2026 research run

Click vs Letta

Letta scores 63.5 (B) on agent readiness against Click's 48.6 (D), and leads in 4 of 7 scored categories. Click leads on schema & documentation, agent ergonomics and security & auth. Both do agent harnesses.

Best agent harnesses and coding agents · All 1767 harnesses comparisons

Best memory layers for AI agents · All 383 memory 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 70
  • Agent ergonomics, 79 against 67
  • Security & auth, 41 against 35

Also in its favour

  • A hosted endpoint, with nothing to install

Watch for

No status page, SLA or public changelog found

Letta B

Best for Long-lived coding agents and assistants that keep memory and identity across sessions and machines.

Ahead on

  • Reliability, 58 against 35
  • Payments & pricing, 90 against 15
  • Maintenance & community, 85 against 25
  • Transparency & trust, 55 against 44

Also in its favour

  • Runs on your own machine
  • Open source

Watch for

The default permission mode is unrestricted, the renamed bypassPermissions, so tool calls aren't confirmed unless the user picks another mode

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 Letta +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.

Letta 90

No x402, MPP or L402 (0 of 40). Per-unit API prices are public, $0.10 per active agent a month and $0.00015 a second of tool execution, plus plan prices (20). A $0 plan with bring-your-own keys; no card is mentioned (20). The CLI runs locally without signing in (20). Total 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 Letta +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.

Letta 85

v0.34.42 on 6 November 2026 (30). Dozens of releases in 90 days (20). Pull requests are merged daily; recent issues from users have few replies (15 of 25). npm and PyPI packages and the Agent SDK track the releases (12 of 15). Lock files, CI and nightly smoke tests (8 of 10). Total 85.

Reliability Letta +23

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.

Letta 58

Local-software lines, read for the harness. @letta-ai/letta-code on npm with Node.js 22.19 or newer, and PyPI wheels for glibc Linux, macOS 14 and Windows x64 with Python 3.9 or newer stated (20). ci.yml, nightly update smoke tests and Telegram live smoke tests exist, but GitHub's API answered with a rate limit, so run results were unread (15 of 25, unchecked). 332 open issues and pull requests, mostly pull requests; recent bug reports such as recall reading the wrong conversation have no reply yet (15 of 25). 398 tags at 0.34.x with release notes on GitHub, no changelog file, and breaking removals such as AgentFile announced in the README (8 of 15). Pre-1.0 (0). Total 58.

Schema & documentation Click +14

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.

Letta 70

Harness reading. docs.letta.com serves llms.txt and a Markdown version of every page, with an applies_to block saying which backend and interface each page covers (10). TypeScript types for the Agent SDK and a documented App Server WebSocket protocol, but no JSON Schema or OpenAPI for the harness (15 of 25). Pages say when to use local or cloud backends, subagents and channels (14 of 20). Permission modes and options are typed in the SDK (12 of 15). Example applications and a remote client reference (11 of 15). Releases most days but no changelog file (8 of 15). Total 70.

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.

Letta 67

Harness reading. Toolsets switch with /model, skills load per agent, and subagents run in the background (18 of 25). Context is managed through memory blocks, reflection and dreaming (12 of 20). letta -p --output-format json for scripted runs and an App Server for programmatic control (12 of 20). Conversations resume by agent and conversation id, and memory is git-tracked so changes can be reverted (15 of 20). Runs with no account on the local backend, with one SDK language, TypeScript (10 of 15). Total 67.

Transparency & trust Letta +11

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.

Letta 55

Apache-2.0 (30). The privacy policy has no date, no legal entity and no retention periods, and says hosted message data may train future models (8 of 30). The README and docs mark AgentFile, the Electron app and the V1 server as deprecated or retired, without dated notice periods (12 of 20). Telemetry is described in the privacy policy only as basic and opt-out when supported; the LETTA_CODE_TELEM=0 switch appears only in the source (5 of 20). Total 55.

Score by category

CategoryWeightClickLettaEdge
Reliability16%3558Letta +23
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8470Click +14
Agent ergonomics13%7967Click +12
Security & auth14%4135Click +6
Payments & pricing10%1590Letta +75
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%2585Letta +60
Transparency & trust7%4455Letta +11
Negative events≤1500
TotalD 48.6/100B 63.5/100

Facts side by side

FactClickLetta
KindHTTP APIAgent harness
VendorClick AI Labs, Inc.Letta
Hosted endpointhttps://api.useclick.ai/v1no (local only)
TransportsHTTP, Streamable HTTPstdio
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.1Apache-2.0
Tools exposed23none
Read-only variant documentednono
llms.txtyesyes
Last release2026-10-192026-11-06
Terms last updated2026-10-12no date given
Privacy policy last updated2026-10-12no date given
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessnot found in the textnot found in the text
Terms restrict benchmarkingnot found in the textnot found in the text
Terms or service can change without noticenot found in the textnot found in the text
Arbitration or class-action waivernot found in the textyes
Popularitynone3.8k stars, 86k npm/wk, 2.2k PyPI/wk

How the scores have moved

Click

No score change since it was listed.

Letta

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.

Letta

Letta's open-source harness gives agents git-tracked memory blocks, skills, subagents and headless JSON runs, with a $0 plan and public per-agent API prices. It starts in the unrestricted permission mode, defaults to Letta Cloud, sends usage telemetry unless LETTA_CODE_TELEM=0 is set, and the V1 API server the comparisons describe is retired.

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

Letta

  1. Start headless runs with an explicit permission mode such as standard or strict; the default auto-approves tools
  2. Pass --backend local for work that must stay on the machine, since Letta Cloud is the default
  3. Set LETTA_CODE_TELEM=0 in unattended runs if usage events must not be sent
  4. Use letta -p --output-format json for scripted runs and parse the JSON, not the terminal output
  5. Don't plan on the retired V1 REST server or .af AgentFile import; both are gone

Questions

Which is better for AI agents, Click or Letta?

Letta scores 63.5 (B) on agent readiness against Click's 48.6 (D), and leads in 4 of 7 scored categories. Click leads on schema & documentation, agent ergonomics and security & auth.

Can an agent call Click and Letta without installing anything?

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

Are Click and Letta open source?

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

Other comparisons with Click or Letta

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.