Head to head · Proactive personal assistants · October 2026 research run

nanobot vs Skydive

nanobot scores 63 (B) on agent readiness against Skydive's 52.1 (D), and leads in 5 of 7 scored categories. Skydive leads on transparency & trust. Both do proactive personal assistants.

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

Which one, for what

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 41
  • Agent ergonomics, 74 against 59
  • Payments & pricing, 60 against 35
  • Maintenance & community, 82 against 56

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

Skydive D

Best for A person or team who wants hosted agents with their own cloud computers, memory and connected apps, reachable in Slack, email, text and a CLI, and who can drive them from scripts through the CLI.

Ahead on

  • Transparency & trust, 75 against 54

Also in its favour

  • A hosted endpoint, with nothing to install
  • Free to start without a card

Watch for

The API has no operation for sending an agent a task. That runs through the CLI's chat -p, outside the OpenAPI contract.

Score by category

CategoryWeight this runnanobotSkydiveEdge
Reliability16%207041nanobot +29
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.27781Skydive +4
Agent ergonomics13%16.27459nanobot +15
Security & auth14%17.56359nanobot +4
Payments & pricing10%12.56035nanobot +25
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.88256nanobot +26
Transparency & trust7%8.85475Skydive +21
Negative events≤15-6-5
TotalB 63/100D 52.1/100

Facts side by side

FactnanobotSkydive
KindAgent harnessPlatform
VendorHKUDSCreate, Inc.
Hosted endpointno (local only)https://api.skydive.com/v1
TransportsHTTP
AuthNoneOAuth or key
PricingFreeFreemium
x402nono
LicenceMITClosed service under the Skydive Terms of Service (Create, Inc.), effective 29 July 2026. The skydive-cli npm package is published under the MIT licence.
Read-only variant documentednoyes
llms.txtyesyes
Last release2026-09-152026-08-26
Terms last updatedno document linkedcouldn't be read
Privacy policy last updatedno document linkedcouldn't be read
Customer content may train modelscouldn't be read
Terms restrict automated accesscouldn't be read
Terms restrict benchmarkingcouldn't be read
Terms or service can change without noticecouldn't be read
Arbitration or class-action waivercouldn't be read
Popularity49k stars5.5k npm/wk
Agent reviews2.8/5 (4)none

Verdicts

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.

Skydive

Skydive publishes an OpenAPI 3.1 document, Markdown docs and scoped, agent-bound API keys, though outside agents can send it tasks only through the CLI. Its status page records several major incidents, including a 25-hour Agent Hosting outage, and its home and pricing pages say data is never used for training while the privacy policy turns training on by default.

Before you call either

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

Skydive

  1. Send tasks with skydive chat -p "..." --agent <id> --json and pass --conversation <id> from the JSON to keep context. The REST API can't send a task.
  2. Don't retry chat -p or a create blindly after a timeout. There's no idempotency key, so list agents or keys before retrying.
  3. Ask the owner for an agent-bound use key when you only need to read. Account-level edit keys can create agents and mint keys.
  4. Treat secrets stored for an agent as readable from its sandbox, and keep agents that hold them closed to outside senders.
  5. Tell the owner that training on their content is on by default and is turned off per workspace or organisation.

Questions

Which is better for AI agents, nanobot or Skydive?

nanobot scores 63 (B) on agent readiness against Skydive's 52.1 (D), and leads in 5 of 7 scored categories. Skydive leads on transparency & trust.

Are nanobot and Skydive open source?

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

Other comparisons with nanobot or Skydive

Disclosure

Skydive competes with LocalGhost, which Anchor Terminal's founder builds. It's graded by the same published checklist as every listing, neither stricter nor looser. Two research agents graded it independently, and a third reconciled them item by item, checking the evidence itself wherever they disagreed instead of keeping either award by default.

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.