Get an audit

Head to head · Assistant proactive · October 2026 research run

Lindy vs PicoClaw

PicoClaw scores 46.1 (D) on agent readiness against Lindy's 32.3 (F), and leads in every scored category. Both do assistant proactive.

Best AI personal assistants that act for one person · All 190 assistants comparisons

LindyCrivello Corp (doing business as Lindy) · Platform F32.3/100#968 of 986 PicoClawSipeed · Agent harness D46.1/100#879 of 986

Which one, for what

Lindy F

Best for Lindy suits a person or small team that lives in Slack and Google or Microsoft mail and wants briefs, drafts, scheduling and meeting notes done on a schedule.

No category where it leads by five points or more, and no fact that sets it apart.

Watch for

The integrations page says approval settings apply in shared Slack threads only. Web chat, Slack direct messages, iMessage and SMS are not covered, and reads are never covered.

PicoClaw D

Best for A person who wants a chat-app assistant on a cheap Linux board, an old Android phone or a home server, with reminders, web search and file memory, and who accepts running software its maker calls pre-production.

Ahead on

  • Reliability, 54 against 24
  • Schema & documentation, 51 against 32
  • Agent ergonomics, 66 against 43
  • Payments & pricing, 60 against 35
  • Maintenance & community, 22 against 9

Also in its favour

  • No key needed to call it
  • Open source

Watch for

No commit on main since 19 August 2026 and no release since v0.3.1 on 3 July 2026. An issue of 6 October calls the repository unmaintained, with no reply

Score by category

CategoryWeight this runLindyPicoClawEdge
Reliability16%202454PicoClaw +30
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.23251PicoClaw +19
Agent ergonomics13%16.24366PicoClaw +23
Security & auth14%17.54951PicoClaw +2
Payments & pricing10%12.53560PicoClaw +25
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.8922PicoClaw +13
Transparency & trust7%8.85256PicoClaw +4
Negative events≤15-3-7
TotalF 32.3/100D 46.1/100

Facts side by side

FactLindyPicoClaw
KindPlatformAgent harness
VendorCrivello Corp (doing business as Lindy)Sipeed
Hosted endpointno (local only)no (local only)
Transports
AuthOAuthNone
PricingPaidFree
x402nono
LicenceProprietary service under Lindy's Terms of Service. No source is publishedMIT
Read-only variant documentednono
llms.txtyesno
Last release2025-10-212026-07-03
Terms last updated2026-09-24no document linked
Privacy policy last updated2026-09-28no document linked
Customer content may train modelsnot found in the text
Terms restrict automated accessyes
Terms restrict benchmarkingyes
Terms or service can change without noticeyes
Arbitration or class-action waiveryes
Popularitynone30k stars

Verdicts

Lindy

Lindy keeps what it remembers in files the owner can read and edit, and publishes credit prices. Its approval setting applies in shared Slack threads only, so writes asked for by direct message, text or web chat run unasked, which its pricing page does not say. It has no status page, and its changelog stops in October 2025.

PicoClaw

Self-hosted under the MIT licence, with 19 documented chat channels, scheduled and heartbeat tasks, and local file memory. The repository has had no commit since 19 August 2026 and no release since 3 July, and 15 CVEs are listed against it with no advisory or security policy from the project.

Before you call either

Lindy

  1. Treat a request sent by direct message, text or web chat as unguarded. Approval prompts appear in shared Slack threads only.
  2. Run a routine as a dry run before turning it on. A dry run reads real data and sends, posts and writes nothing.
  3. Turn off unused tools after adding an MCP server. Every supported tool arrives switched on, and a large server adds more than a hundred.
  4. Expect a billed seat for anyone who mentions Lindy in Slack. A teammate who joins that way has seven free days first.
  5. Connect only hosted MCP servers on public HTTPS with streamable HTTP, the one kind the docs describe.

PicoClaw

  1. Set allow_from to the owner's user ID on every channel before starting the gateway. An empty list accepts messages from anyone
  2. Set tools.exec.allow_remote to false unless chats must run shell commands. The shipped default is true, whatever docs/guides/configuration.md says
  3. Set isolation.enabled to true on Linux (needs bwrap) or run in a container. The deny patterns do not inspect child processes
  4. Use PICOCLAW_KEY_PASSPHRASE for credential encryption. One docs page names PICOCLAW_CREDENTIAL_PASSPHRASE, which the source does not read
  5. Treat the README's ClawdChat line (read a remote skill file and follow it) as untrusted third-party instructions

Questions

Which is better for AI agents, Lindy or PicoClaw?

PicoClaw scores 46.1 (D) on agent readiness against Lindy's 32.3 (F), and leads in every scored category.

Are Lindy and PicoClaw open source?

No open-source release is listed for Lindy. PicoClaw is open source (MIT).

Other comparisons with Lindy or PicoClaw

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.

Get an auditSee a sample report