Get an audit

Head to head · Assistant proactive · October 2026 research run

Lindy vs nanobot

nanobot scores 62.4 (B) on agent readiness against Lindy's 32.3 (F), and leads in 6 of 7 scored categories. 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 nanobotHKUDS · Agent harness B62.4/100#446 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.

Also in its favour

  • Free to start without a card

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.

nanobot B

Best for A technical owner who wants an assistant on their own machine across many chat apps, with file-based memory and a free choice of model.

Ahead on

  • Reliability, 70 against 24
  • Schema & documentation, 77 against 32
  • Agent ergonomics, 74 against 43
  • Security & auth, 63 against 49
  • Payments & pricing, 60 against 35
  • Maintenance & community, 82 against 9

Also in its favour

  • No key needed to call it
  • Open source

Watch for

No per-action approval was found in the docs or source. The agent sends messages, runs shell commands and edits files without asking

Score by category

CategoryWeight this runLindynanobotEdge
Reliability16%202470nanobot +46
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.23277nanobot +45
Agent ergonomics13%16.24374nanobot +31
Security & auth14%17.54963nanobot +14
Payments & pricing10%12.53560nanobot +25
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.8982nanobot +73
Transparency & trust7%8.85248Lindy +4
Negative events≤15-3-6
TotalF 32.3/100B 62.4/100

Facts side by side

FactLindynanobot
KindPlatformAgent harness
VendorCrivello Corp (doing business as Lindy)HKUDS
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.txtyesyes
Last release2025-10-212026-09-15
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
Popularitynone49k 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.

nanobot

nanobot runs on the owner's machine under the MIT licence, with no telemetry found in its source and memory kept as files the owner can read and restore. No per-action approval step was found, and the shell sandbox and workspace restriction are off by default. Five security advisories were published between March and September 2026, all with fixes.

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.

nanobot

  1. Set tools.restrictToWorkspace to true and tools.exec.sandbox to bwrap or seatbelt before giving it real accounts. Both are off by default
  2. Run 0.3.0 or later. Earlier versions carry the published SSRF flaw in web fetch (GHSA-vc5v-6vwm-wf9m)
  3. Keep allowFrom narrow on every channel and never set ["*"] on Email, which has no pairing
  4. Write secrets as ${VAR} references in ~/.nanobot/config.json. Plain values are stored in clear text
  5. Use nanobot -m "..." for a one-shot run, and keep nanobot gateway running for channels, schedules and heartbeat

Questions

Which is better for AI agents, Lindy or nanobot?

nanobot scores 62.4 (B) on agent readiness against Lindy's 32.3 (F), and leads in 6 of 7 scored categories.

Are Lindy and nanobot open source?

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

Other comparisons with Lindy or nanobot

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