Discofork
Repository brief

HKUDS/nanobot

Read the upstream summary on the left, browse the cached forks below it, and load each fork comparison into the right-hand panel.

Cached analysis
cached 2026-03-30T16:00:25.411Z
1mo ago

HKUDS/nanobot

HKUDS/nanobot is a Python 3.11+ MIT-licensed personal AI assistant framework with strong momentum: 37,091 stars, 6,384 forks, and active commits on 2026-03-30. The repository positions itself as an ultra-lightweight alternative to OpenClaw and currently ships as `nanobot-ai` version `0.1.4.post6`.

GitHub
Loading tags...
Stars37,091
Forks6,384
Default branchmain
Last pushed2026-03-30T15:40:05Z
Recommended shortcuts

Jump straight into Discofork's strongest cached fork picks, or open a compare view in one click.

Forks

Choose a fork to inspect

10 of 10 fork briefs
Selected

Choose this fork if you want a companion-oriented nanobot with richer persona, memory, and media workflows. Stick with upstream if you want the leanest, most current general assistant framework and do not need the SillyTavern-specific layer.

Choose upstream unless you specifically need this fork's older snapshot or private branding path. As a product fork, it adds no visible capability and is far behind the maintained upstream.

Choose this fork if Feishu support and custom provider onboarding matter more than staying current with upstream. Avoid it if you want the latest nanobot API/security work or a broadly maintained base.

Prefer upstream unless you specifically want a frozen personal fork. This fork adds no visible functionality and is behind on recent API, channel, and security work, so it is mainly useful as a stable baseline rather than a better distribution.

Choose this fork if you want a more personal, memory-heavy assistant with coaching and daemon workflows. Choose upstream if you need current integrations, lower maintenance risk, or compatibility with nanobot's fast-moving API and channel support.

Choose this fork if you want a more opinionated local assistant with session archival and custom workflow changes. Choose upstream if you need broad platform coverage, faster parity with recent API work, or lower long-term maintenance cost.

Choose this fork if you want an interview-centric assistant with opinionated workflows and curated knowledge handling. Choose upstream if you need the broader, more current nanobot platform with less drift and more general-purpose integrations.

Choose this fork if you want a more opinionated, operationally packaged nanobot for Honcho-style use. Choose upstream if you want the newest features, security fixes, and the widest compatibility with the least merge debt.

Choose this fork only if its extra agent-tooling and custom-provider changes are the point. For most adopters, upstream is the safer default because this fork is materially behind and misses recent API, channel, and security work.

Choose this fork if you want a more opinionated OpenAI-compatible variant with better onboarding and memory behavior. Choose upstream instead if you need the latest platform support, security fixes, and active release momentum.