Nanobot unifies its setup guides and shows the workbench behind the small core

Nanobot's September 7 documentation changes make its product easier to recognize without announcing new runtime code. One merged change replaces a separate personal-agent pip-and-wizard path with links to the maintained Quick Start. Another refreshes the README with a browser-workbench gallery and current terminal capabilities. Together they address an adoption problem: a small-core description no longer tells newcomers what the surrounding application can do, or which features their installation actually includes.

The facts

- The personal-agent guide now delegates installation and initial model setup to Quick Start instead of maintaining a parallel flow. - The installation guidance explicitly warns that main-branch documentation may be newer than the installed stable package and links to stable guidance. - The README gallery includes grouped conversations, file diffs, context usage, MCP Apps and Automations rather than only a command-line introduction. - The gallery change identifies demonstration conversations, usage figures and paused schedules as demo material instead of live production observations. - The current README separates stable package installs from editable source checkouts and tells users to update through the same chosen track. - The source says the first-useful-task tutorial remains follow-up work, and the gallery verification did not exercise live inference or scheduled delivery.

Why it matters

Documentation is part of the product when the first installation has several entry points. Divergent instructions can make a working package look broken, or make source-only behavior look like a missing configuration setting. Nanobot now presents a broader agent workbench while retaining its small, readable-core positioning. That is a meaningful adoption signal, but not a reason to flatten the stable/source distinction. The current README's description of bundled interfaces must be read with the installation track and version in mind. A screenshot can show intended interaction and still tell an operator nothing about their own model connection or message delivery.

Current

Inspected on 2026-09-08. The Nanobot stable-release baseline is v0.3.0 published 2026-07-25T08:08:47Z. The main source was closed when captured. Release metadata is a version boundary, not evidence that an open proposal has shipped.

Evidence

The primary source is HKUDS/nanobot PR #5690 (https://github.com/HKUDS/nanobot/pull/5690). Supporting context comes from HKUDS/nanobot PR #5684 (https://github.com/HKUDS/nanobot/pull/5684); Nanobot — current project README (https://raw.githubusercontent.com/HKUDS/nanobot/main/README.md). The linked records were inspected directly; related project records are not independent confirmations.

Operator take

Choose the installation track before following a screenshot-driven tutorial. Record the installed version, use the matching Quick Start and verify one real task through the selected interface. For a source checkout, keep Python, WebUI and terminal assets aligned rather than mixing a new guide with an old package. The merged documentation work is useful because it centralizes the route to setup and makes capabilities discoverable; the next acceptance milestone is the first meaningful end-to-end task. The gallery's explicit demo labels are worth preserving in downstream tutorials. They prevent illustrative token figures or paused schedules from turning into unsupported performance or automation claims as screenshots circulate through comparison sites.

Caveat

These are merged documentation and positioning changes, not a September runtime release. The inspected stable release remains v0.3.0; source documentation can describe later work, and author-reported UI tests do not establish live provider or delivery health.