Index / nanobot · updated Oct 24, 2026

nanobot

HKUDS/nanobot · healthy · rank 3 of 50 by stars

An ultra-lightweight (~4,000-line) Python rewrite of OpenClaw that packs WebUI, memory, MCP, multi-agent delegation, and automation into a readable core. It's one of the most actively iterated OpenClaw alternatives with a huge star count and frequent releases.

#python#self-hosted#lightweight#multi-agent#openclaw-alternative
Compare vs OpenClaw
GitHub ↗

Facts

Repository

Contributors498
Open issues869
Last commitOct 20, 2026
Release cadence~19 days
Latest releasev0.3.5

Runtime

LanguagePython
Memory1.5 MB
Boot time8 ms
Deploymentself-hosted · desktop · cloud
Setup difficultyLow
Plugin ecosystemEmerging

Posture

LicenseMIT
Local-firstYes
Cloud dependencyOptional
Multi-userNo
Privacy postureStrong

Community

Sentiment78% positive
Reddit mentions4
Web results10

Security breakdown

Composite 62 / 100 · how these are scored

Sandboxing4 / 10

higher is safer

API security6 / 10

higher is safer

Network isolation4 / 10

higher is safer

Telemetry safety7 / 10

higher is safer

Shell access risk7 / 10

higher is riskier

Model access

Read from the repository, not written by a model · 94 files examined

5 providers · gateway support

Direct
AnthropicAzure OpenAIAWS BedrockGroqOpenAI
Gateway
OpenRouter
Compatible
OpenAI-compatible

Pinned models

gpt-5.4OpenAI

claude-opus-4-7 released 2026-04-16 — 6 months old (from the public model catalogue)

Pin last edited 16 days ago

Several defaults are pinned; the project picks one per provider rather than shipping a single default.

Evidence

Decision

Why choose nanobot over OpenClaw?

Why choose this

  • Dramatically smaller, more readable codebase (~4k lines) that's easy to audit and modify
  • Very fast, lightweight startup compared to OpenClaw's heavier footprint
  • Broad provider support (46 providers) with model routing

Tradeoffs

  • Smaller community and governance structure than OpenClaw's massive ecosystem
  • Less mature sandboxing and security hardening for tool/shell execution
  • Plugin ecosystem is emerging rather than established

Best fit

  • Users wanting a small, readable OpenClaw alternative in Python
  • Self-hosters who want WebUI, terminal, and chat-app access in one gateway
  • Tinkerers who want MCP, memory, and automation without a heavy codebase

Avoid if

  • You need hardened container sandboxing for untrusted tool execution
  • You require enterprise-grade governance and extended-stable release channels
  • You want a large plugin marketplace rather than an emerging ecosystem
High Confidence80%

Evidence is solid: rich README, active recent commits, a dated v0.3.5 release, and multiple ecosystem digests confirm active development. Uncertainty remains around sandboxing depth and multi-user support, which are not clearly documented in the provided sources.

AI layer reviewed Oct 5, 2026 · how this is written

Star activity

49,325 stars today

Overview

nanobot is an ultra-lightweight, open-source, self-hosted personal AI agent framework written in Python (3.11+), positioned as a compact rewrite of OpenClaw at roughly 4,000 lines of readable core code. Despite its small footprint, it ships a full feature set: a WebUI, terminal UI, chat-app integrations (Telegram, Discord, WhatsApp), tool use, long-term memory, MCP integrations, model routing across 46 providers, multi-agent delegation, scheduled automation with a calendar view, and an OpenAI-compatible API.

Architecturally, nanobot runs as a long-lived gateway service (nanobot gateway) that can be operated headless or with the WebUI, making it familiar to users coming from OpenClaw who already run agents as services. Recent commits show active investment in subagent session-owned task messaging and cancellation, WebUI mobile/touch polish, and provider compatibility fixes (e.g., GPT-6 temperature handling), indicating a fast-moving, well-maintained codebase with CI and PyPI distribution (nanobot-ai).

Compared to OpenClaw, nanobot trades ecosystem scale and governance for simplicity and auditability: it's far easier to read, modify, and self-host, with strong local-first privacy posture and optional cloud model dependency. However, its sandboxing and security hardening are less documented, and its plugin ecosystem is still emerging, so production-critical or multi-tenant deployments may still favor OpenClaw's mature release channels and larger community.

Nominate a clone

Add a new Claw

Paste a GitHub repository and tell us why it belongs on the tracker.

Opens a prefilled issue on GitHub — every nomination is public. Comfortable with a PR? Adding the repo to projects.json is faster.