a6b059d379
Reasoning was being shipped to every channel as a generic progress message with a `_reasoning: true` flag. Two problems with that: 1. Channels without a low-emphasis UI primitive (Telegram, Slack, Discord, Feishu...) would dump raw model thoughts as ordinary replies, polluting the conversation. 2. The agent loop double-gated by inspecting `channels_config`, which coupled the loop to display policy. Treat reasoning as its own plugin action — `BaseChannel.send_reasoning` defaults to a documented no-op; channels that have a fitting affordance override. ChannelManager routes `_reasoning` outbounds to that method only when the channel opts in via `show_reasoning` (camelCase alias `showReasoning` mirrors `sendProgress`). Plugins that don't override silently drop reasoning — "no fit, no leak" is the contract. Reference implementation lands for WebSocket / WebUI: a new `kind: "reasoning"` frame, parked on the active assistant bubble as a collapsible `Thinking` group above the answer. CLI keeps its existing direct path (it doesn't go through the bus). `ChannelsConfig.show_reasoning` flips to `true` by default — only adapted channels surface anything, others stay quiet. Loop net diff is -3 lines: the `channels_config.show_reasoning` check moves out, leaving emit_reasoning a one-liner that publishes and trusts the channel to decide. Co-authored-by: Cursor <cursoragent@cursor.com>
nanobot webui
The browser front-end for the nanobot gateway. It is built with Vite + React 18 + TypeScript + Tailwind 3 + shadcn/ui, talks to the gateway over the WebSocket multiplex protocol, and reads session metadata from the embedded REST surface on the same port.
For the project overview, install guide, and general docs map, see the root
README.md.
Current status
Note
The standalone WebUI development workflow currently requires a source checkout.
WebUI changes in the GitHub repository may land before they are included in the next packaged release, so source installs and published package versions are not yet guaranteed to move in lockstep.
Layout
webui/ source tree (this directory)
nanobot/web/dist/ build output served by the gateway
Develop from source
1. Install nanobot from source
From the repository root:
pip install -e .
2. Enable the WebSocket channel
In ~/.nanobot/config.json:
{ "channels": { "websocket": { "enabled": true } } }
3. Start the gateway
In one terminal:
nanobot gateway
4. Start the WebUI dev server
In another terminal:
cd webui
bun install # npm install also works
bun run dev
Then open http://127.0.0.1:5173.
By default, the dev server proxies /api, /webui, /auth, and WebSocket
traffic to http://127.0.0.1:8765.
If your gateway listens on a non-default port, point the dev server at it:
NANOBOT_API_URL=http://127.0.0.1:9000 bun run dev
Access from another device (LAN)
To use the webui from another device on the same network, set host to "0.0.0.0" and configure a token or tokenIssueSecret in ~/.nanobot/config.json:
{
"channels": {
"websocket": {
"enabled": true,
"host": "0.0.0.0",
"port": 8765,
"tokenIssueSecret": "your-secret-here"
}
}
}
The gateway will refuse to start if host is "0.0.0.0" and neither token nor tokenIssueSecret is set.
Then open http://<your-ip>:8765 on the other device. The webui will show an authentication form where you enter the secret. It is saved in your browser so you only need to enter it once.
Build for packaged runtime
cd webui
bun run build
This writes the production assets to ../nanobot/web/dist, which is the
directory served by nanobot gateway and bundled into the Python wheel.
If you are cutting a release, run the build before packaging so the published wheel contains the current WebUI assets.
Test
cd webui
bun run test
Acknowledgements
agent-chat-uifor UI and interaction inspiration across the chat surface.