Head to head · Assistants reached by message · October 2026 research run
nanobot vs Tab
nanobot scores 62.4 (B) on agent readiness against Tab's 10.7 (F), and leads in every scored category. Both do assistants reached by message.
Best AI personal assistants that act for one person · All 834 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 5
- Schema & documentation, 77 against 0
- Agent ergonomics, 74 against 0
- Security & auth, 63 against 4
- Payments & pricing, 60 against 0
- Maintenance & community, 82 against 58
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
Tab F
Best for A person who wants a texting assistant that browses, calls and buys with tight checkout controls.
Also in its favour
- No incidents deducted, where nanobot loses 6 points for them
Watch for
Private beta behind a waitlist.
Score by category
| Category | Weight this run | nanobot | Tab | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 70 | 5 | nanobot +65 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 77 | 0 | nanobot +77 |
| Agent ergonomics | 13%16.2 | 74 | 0 | nanobot +74 |
| Security & auth | 14%17.5 | 63 | 4 | nanobot +59 |
| Payments & pricing | 10%12.5 | 60 | 0 | nanobot +60 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 82 | 58 | nanobot +24 |
| Transparency & trust | 7%8.8 | 48 | 45 | nanobot +3 |
| Negative events | ≤15 | -6 | 0 | |
| Total | B 62.4/100 | F 10.7/100 |
Facts side by side
| Fact | nanobot | Tab |
|---|---|---|
| Kind | Agent harness | Platform |
| Vendor | HKUDS | Terrasoft, Inc. |
| Hosted endpoint | no (local only) | no (local only) |
| Transports | ||
| Auth | None | OAuth or key |
| Pricing | Free | Paid |
| x402 | no | no |
| Licence | MIT | Closed service under Tab's Terms of Use (Terrasoft, Inc., effective 2 September 2026). |
| Read-only variant documented | no | no |
| llms.txt | yes | no |
| Last release | 2026-09-15 | none |
| Terms last updated | no document linked | |
| Privacy policy last updated | no 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 | ||
| Popularity | 49k stars | 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.
Tab
Tab is a private-beta texting assistant with a detailed security page on credential isolation and checkout binding, and a public updates page. No outside agent can call it, no price is published, and its privacy policy says nothing on training with user content.
Before you call either
nanobot
- Set
tools.restrictToWorkspaceto true andtools.exec.sandboxtobwraporseatbeltbefore giving it real accounts. Both are off by default - Run 0.3.0 or later. Earlier versions carry the published SSRF flaw in web fetch (GHSA-vc5v-6vwm-wf9m)
- Keep
allowFromnarrow on every channel and never set["*"]on Email, which has no pairing - Write secrets as
${VAR}references in~/.nanobot/config.json. Plain values are stored in clear text - Use
nanobot -m "..."for a one-shot run, and keepnanobot gatewayrunning for channels, schedules and heartbeat
Tab
- Don't plan to call Tab from another agent. It answers only the owner's Messages or WhatsApp thread.
- Tell the owner that access needs a waitlist place and no price is published.
Questions
Which is better for AI agents, nanobot or Tab?
nanobot scores 62.4 (B) on agent readiness against Tab's 10.7 (F), and leads in every scored category.
Are nanobot and Tab open source?
nanobot is open source (MIT). No open-source release is listed for Tab.
Other comparisons with nanobot or Tab
- asaply vs nanobot
- asaply vs Tab
- Asmi vs nanobot
- Asmi vs Tab
- AstrBot vs Tab
- Boba vs nanobot
- Boba vs Tab
- Boski vs Tab
- Brea vs nanobot
- Brea vs Tab
- Caddy vs Tab
- CowAgent vs Tab
- Del vs nanobot
- Del vs Tab
- folk vs Tab
- GAIA vs Tab
- Grok Bot vs Tab
- Haven vs Tab
- Hermes Agent vs Tab
- HireAlpha vs nanobot
- HireAlpha vs Tab
- Instinct vs Tab
- IronClaw vs Tab
- Lindy vs Tab
- nanobot vs OpenInstinct
- nanobot vs Orbits
- nanobot vs Orchid
- nanobot vs szn
- nanobot vs Zapia
- NanoClaw vs Tab
- Natura tinyNature vs Tab
- Dots vs Tab
- OpenClaw vs Tab
- OpenInstinct vs Tab
- Orbits vs Tab
- Orchid vs Tab
- Pally vs Tab
- PicoClaw vs Tab
- Poke vs Tab
- QwenPaw vs Tab
- szn vs Tab
- Tab vs Tomo
- Tab vs Town
- Tab vs Zapia
- Tab vs ZeroClaw
- Tab vs Zo Computer
- AstrBot vs nanobot
- Boski vs nanobot
- Caddy vs nanobot
- CowAgent vs nanobot
- folk vs nanobot
- GAIA vs nanobot
- Gemini Spark vs nanobot
- Grok Bot vs nanobot
- Haven vs nanobot
- Hermes Agent vs nanobot
- Instinct vs nanobot
- IronClaw vs nanobot
- Leon vs nanobot
- Lindy vs nanobot
- nanobot vs NanoClaw
- nanobot vs Dots
- nanobot vs OpenClaw
- nanobot vs PicoClaw
- nanobot vs Poke
- nanobot vs QwenPaw
- nanobot vs Town
- nanobot vs ZeroClaw
- nanobot vs Zo Computer
- nanobot vs Natura tinyNature
- nanobot vs Pally
- nanobot vs Tomo
- nanobot vs Wajo (Fo)
- Gemini Spark vs Tab
- Leon vs Tab
- nanobot vs Talorys
- Tab vs Talorys
- Tab vs Wajo (Fo)
Disclosure
Tab 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
- This page as Markdown
/compare/nanobot-vs-tab-bot.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/nanobot.json·/api/v1/tools/tab-bot.json - From a terminal
anchor compare nanobot tab-bot(the CLI) - Over MCP
compare_tools {"a": "nanobot", "b": "tab-bot"}at/mcp, no key