Get an audit

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

nanobot vs Town

nanobot scores 62.4 (B) on agent readiness against Town's 48.7 (D), and leads in 5 of 7 scored categories. Town leads on security & auth and transparency & trust. Both do proactive personal assistants.

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

nanobotHKUDS · Agent harness B62.4/100#446 of 1010 TownTown.com, Inc. · Platform D48.7/100#834 of 1010

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 35
  • Schema & documentation, 77 against 33
  • Agent ergonomics, 74 against 49
  • Payments & pricing, 60 against 30
  • Maintenance & community, 82 against 60

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

Town D

Best for An owner who wants a mail and calendar assistant whose routines other systems can trigger.

Ahead on

  • Security & auth, 79 against 63
  • Transparency & trust, 63 against 48

Also in its favour

  • Free to start without a card
  • No incidents deducted, where nanobot loses 6 points for them

Watch for

The privacy policy describes training with an opt-out and the trust page says training is opt-in.

Score by category

CategoryWeight this runnanobotTownEdge
Reliability16%207035nanobot +35
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.27733nanobot +44
Agent ergonomics13%16.27449nanobot +25
Security & auth14%17.56379Town +16
Payments & pricing10%12.56030nanobot +30
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.88260nanobot +22
Transparency & trust7%8.84863Town +15
Negative events≤15-60
TotalB 62.4/100D 48.7/100

Facts side by side

FactnanobotTown
KindAgent harnessPlatform
VendorHKUDSTown.com, Inc.
Hosted endpointno (local only)no (local only)
TransportsHTTP
AuthNoneOAuth or key
PricingFreeFreemium
x402nono
LicenceMITClosed service under Town's Terms of Service (Town.com, Inc., updated 21 July 2026).
Read-only variant documentednoyes
llms.txtyesno
Last release2026-09-152026-10-10
Terms last updatedno document linked
Privacy policy last updatedno document linked
Customer content may train models
Terms restrict automated access
Terms restrict benchmarking
Terms or service can change without notice
Arbitration or class-action waiver
Popularity49k starsnone

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.

Town

Town is a hosted assistant that works across the owner's mail, calendar and work apps, and other systems can start its routines through per-routine webhooks with rotatable secrets, idempotency keys and documented errors. A caller can't read a run's result. The privacy policy and trust page disagree on whether training is 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

Town

  1. Start a Town routine with POST to its webhook URL, Authorization Bearer whsec_ secret, and application/json or text/plain. Expect 202 only.
  2. Send X-Town-Idempotency-Key with a stable event id on every retry so Town doesn't start a second run.
  3. Treat 404 as wrong secret, disabled endpoint or missing endpoint alike, and ask the owner to check Routine Settings rather than retrying.
  4. Send account_email only if the owner allowed the override. It must match a connected account in full and can't widen the routine's scope.
  5. Ask the owner to keep routines that act on webhook input in approval-required mode, as Town's own docs advise.

Questions

Which is better for AI agents, nanobot or Town?

nanobot scores 62.4 (B) on agent readiness against Town's 48.7 (D), and leads in 5 of 7 scored categories. Town leads on security & auth and transparency & trust.

Are nanobot and Town open source?

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

Other comparisons with nanobot or Town

Disclosure

Town 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.

Get an auditSee a sample report