nanobot

最近の更新

• v0.3.5 2026年9月15日
  リリースノート（原文）

  🐈 **nanobot `v0.3.5`** brings the workbench to the terminal — and makes conversations easier to continue across the browser, terminal, and chat apps.
  
  The headline is **one agent, more places to work**. Run `nanobot` for the native terminal client or `nanobot webui` for the browser. Both use the same gateway and saved WebSocket conversations. Terminal sessions can be resumed, forked, inspected, and detached without building a separate agent runtime.
  
  The browser workbench has grown around real multitasking: grouped conversation panes, temporary chats, persistent sidebar ordering, session mentions, a skills marketplace, portable Agent Plugins, and browser OAuth for remote MCP servers. Automations now have task and calendar views, clearer scheduling controls, and per-run replies. Mobile comp…

• v0.3.0 2026年7月25日
  リリースノート（原文）

  🐈 **nanobot `v0.3.0`** is here: **260 PRs merged and 38 new contributors**. The agent gained agency.
  
  The fastest way to experience the release is one command:
  
  ```bash
  nanobot webui
  ```
  
  It prepares the local WebUI, starts the gateway, and opens the browser workbench. On a fresh install, guided setup helps you choose a provider and configure access without beginning in a JSON file. The published package already includes the WebUI, so there is no separate frontend build.
  
  The product story is **a WebUI that now feels like the front door to nanobot**. Chats read as topics; documents, quoted follow-ups, multimodal tool results, file diffs, code previews, and model fallback are visible in the conversation. Model presets can be switched from the composer, native desktop hosts can ope…

• v0.2.2 2026年6月23日
  リリースノート（原文）

  🐈 **nanobot `v0.2.2`** is here — 140 PRs merged, 21 new contributors. The agent got sturdier!
  
  The headline is **durability**. WebUI conversations now survive more of real life: transcripts are segmented instead of living in one fragile file, forked chats preserve replies more reliably, active turns scroll and replay more predictably, startup paths block less, and gateway shutdown is much calmer. Long sessions, stale providers, slow routes, broken config files, malformed history, stream stalls, and empty provider responses all got less likely to derail the work.
  
  The second story is **nanobot becoming a real Python runtime**. The SDK is no longer just a thin convenience layer around the agent loop: concurrent `run()` calls are isolated, hooks are cleaner, MCP lifecycle handling is safe…