Get an audit

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

NanoClaw vs Town

NanoClaw scores 68.3 (B) on agent readiness against Town's 48.7 (D), and leads in 6 of 7 scored categories. Town leads on security & auth. Both do proactive personal assistants.

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

NanoClawNanoCo, Inc. · Agent harness B68.3/100#229 of 1010 TownTown.com, Inc. · Platform D48.7/100#834 of 1010

Which one, for what

NanoClaw B

Best for A technical owner who wants an assistant on their own machine, reachable from chat apps, with container isolation and scheduled tasks, and who is willing to keep a fork.

Ahead on

  • Reliability, 78 against 35
  • Schema & documentation, 82 against 33
  • Agent ergonomics, 70 against 49
  • Payments & pricing, 60 against 30
  • Maintenance & community, 78 against 60

Also in its favour

  • No key needed to call it
  • Open source

Watch for

The Claude provider runs with permissionMode: 'bypassPermissions', so shell, file and web tools run inside the container with no prompt

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 74

Also in its favour

  • No incidents deducted, where NanoClaw loses 5 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 runNanoClawTownEdge
Reliability16%207835NanoClaw +43
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.28233NanoClaw +49
Agent ergonomics13%16.27049NanoClaw +21
Security & auth14%17.57479Town +5
Payments & pricing10%12.56030NanoClaw +30
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.87860NanoClaw +18
Transparency & trust7%8.86563NanoClaw +2
Negative events≤15-50
TotalB 68.3/100D 48.7/100

Facts side by side

FactNanoClawTown
KindAgent harnessPlatform
VendorNanoCo, Inc.Town.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-10-092026-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
Popularity31k starsnone

Verdicts

NanoClaw

Each session runs in an unprivileged Docker container and API keys stay in a credential gateway on the host, so a manipulated agent cannot read them. Inside the container the agent runs with permission prompts off, network egress is open by default, and it can message any chat it is wired to without approval.

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

NanoClaw

  1. Install with git clone and bash nanoclaw.sh. There is no registry package, and setup needs Docker, Node 22 or later and a Claude or Codex credential
  2. Set NANOCLAW_EGRESS_LOCKDOWN=true before giving an agent credentials or an audience of strangers. The default leaves egress open
  3. Put chats with different audiences in separate agent groups. Every session of a group shares one read-write workspace and memory tree
  4. Turn on per-request approval for a secret in the gateway when its use should wait for a person. It is off unless configured
  5. On OneCLI installs, move the gateway to 1.42.0 by the upgrade guide before updating to 2026.10.0. The updater stops until that is done

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, NanoClaw or Town?

NanoClaw scores 68.3 (B) on agent readiness against Town's 48.7 (D), and leads in 6 of 7 scored categories. Town leads on security & auth.

Are NanoClaw and Town open source?

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

Other comparisons with NanoClaw 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