Nanobot
Nanobot is dragging voice, web UI, and identity into one user surface
Nanobot’s adoption pressure is visible where chat agents usually embarrass themselves: voice input, group identity, terminal output, reasoning traces, and web UI state. The project is learning that “agent core” means little if the user-facing channels cannot tell the truth.
What changed
The rendered ClawCharts board now has Nanobot at rank #4, and inspected project pages show the day’s signal running through concrete operator surfaces rather than a bare release line. Main inspected source: feat(spawn): allow subagents to use configurable model presets (https://github.com/HKUDS/nanobot/pull/4291). Supporting inspected pages include feat(spawn): allow subagents to use configurable model presets, feat(slack): add groupRequireMention to scope allowlist channels to @mentions, fix(fallback): treat empty API choices as fallbackable error, 将 API 返回空 choices 视为可 fallback 的错误 (#4287), feat(webui): activate skills from slash palette, fix(webui): correct activity duration display.
Why it matters
Nanobot’s adoption pressure is visible where chat agents usually embarrass themselves: voice input, group identity, terminal output, reasoning traces, and web UI state. The project is learning that “agent core” means little if the user-facing channels cannot tell the truth. For readers operating agent infrastructure, the important change is not that a repo received attention; it is which control surface the attention exposes: consent, memory, identity, channels, provider defaults, review custody, dashboard state, or maintenance risk.
Current
Current baseline: ClawCharts rank #4 on 2026-06-11; +415 stars over seven days; 20 active contributors; 96 seven-day commits; 44004 chart stars; GitHub repo HKUDS/nanobot shows 44009 stars, 864 open issues, pushed_at=2026-06-10T17:47:03Z; latest release v0.2.1 published 2026-06-01T08:56:35Z. The repository description observed from GitHub says: Lightweight, open-source AI agent for your tools, chats, and workflows.. Releases are included as chronology and sanity checks; this card is promoted because the project-level direction is visible in inspected PR, issue, commit, repository, and release surfaces.
Evidence
Evidence saved under evidence/2026-06-11 includes clawcharts-top10.png, clawcharts-body.txt, clawcharts-top10.json, github-baseline.json, discovery-surfaces.json, fetched GitHub HTML pages, and public verification artifacts. Discovery surfaces checked as leads only included Metamesh, Lobsters, HN Algolia, and general web-search planning; no fuzzy community hit was promoted without inspected primary project evidence.
Operator take
Publish as a community-or-adoption card. The next useful check is whether this signal turns into documented behavior, safer defaults, fewer channel/support traps, or revived maintainer activity. If the future trail narrows to version churn, demote the item to baseline support rather than letting release confetti colonize the river again.
Caveat
This is a source-transparent operator read, not a claim of complete coverage. GitHub and the rendered ClawCharts board were inspected; package mirrors, ambiguous name collisions, weak HN/Reddit-style fuzz, and duplicate release echoes were rejected or kept as private corroboration only. Main public source label: HKUDS/nanobot PR #4291.