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.
patchy631/nanobot
stale
significant_divergence
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.
ttxiaotaoge/SkyLeap-nanobot
stale
significant_divergence
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.
dragosroua/aigernon
stale
significant_divergence
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.
kspviswa/sarathy
slowing
significant_divergence
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.
YH7916/Interview-Copilot
slowing
significant_divergence
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.
plastic-labs/nanobot-honcho
slowing
significant_divergence
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.
carterwayneskhizeine/nanobot
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.