BioRouter v1.80.1
BioRouter v1.80.1 Release Notes
Release Date: June 2026
Repository: github.com/BaranziniLab/BioRouter
A patch release on top of v1.80.0 that makes the Knowledge feature fully usable from chat. You can now create, curate, visualize, and move knowledge bases entirely by talking to the agent — no need to switch to the Knowledge tab — and the graph view stays in sync with what the agent writes. No breaking changes.
Downloads
| Platform | File | Install |
|---|---|---|
| macOS (Apple Silicon) | BioRouter-1.80.1-arm64.dmg |
Open the DMG and drag BioRouter.app to /Applications |
| macOS (Intel) | BioRouter-1.80.1-x64.dmg |
Open the DMG and drag BioRouter.app to /Applications |
| Windows (x64) | BioRouter-win32-x64-1.80.1.zip |
Unzip and run BioRouter.exe |
| Linux Ubuntu / Pop!_OS (x64) | biorouter_1.80.1_amd64.deb |
sudo dpkg -i biorouter_1.80.1_amd64.deb |
| Linux Fedora / RHEL (x64) | BioRouter-1.80.1-1.x86_64.rpm |
sudo rpm -i BioRouter-1.80.1-1.x86_64.rpm |
What's Fixed
Knowledge bases curated from chat now visualize in the graph
When the agent authored knowledge pages from chat (via kb_write_page), the derived graph cache was never rebuilt, so the Knowledge tab showed 0 pages · 0 links even though the pages existed and cross-linked each other — and the Refresh graph button couldn't recover them because it only re-read the stale cache. kb_write_page now rebuilds the graph cache on every write (mirroring source ingestion), so pages and [[wiki-links]] the agent creates appear in the force-graph immediately.
The Knowledge tab reflects bases created from chat without a reload
The Knowledge view fetched its base list only once at app start, so a knowledge base the agent created in a chat wouldn't appear in the KB selector until a full app reload. The view now re-fetches the base list when it mounts and whenever the KB-selector palette opens, so chat-created bases show up right away.
Imported knowledge bases keep a consistent id
Importing a .brkb archive whose base id collided with an existing one assigned a deduplicated folder id (e.g. cardio-test-2) but left the archived manifest.yaml pointing at the original id — so the imported base displayed under the source's id and collided with it in the list. The importer now rewrites the manifest id to match the new folder/registry id.
What's New
First-class .brkb export / import from chat
Two new knowledge tools — kb_export and kb_import — let the agent write a knowledge base to a .brkb archive on disk and load one back in directly, instead of shelling out to zip the folder. Combined with the existing primitives, every Knowledge GUI operation (create, ingest, curate, lint, visualize, export, import) is now achievable purely by chatting with the agent.
Upgrading
No manual migration needed. Replace your existing installation with the new package for your platform.
- macOS: open the new DMG and drag
BioRouter.appto/Applications, overwriting the existing copy - Linux:
sudo dpkg -i biorouter_1.80.1_amd64.deborsudo rpm -U BioRouter-1.80.1-1.x86_64.rpm - Windows: unzip and replace the existing installation folder
Existing knowledge bases are unaffected. A base created or curated before this release will populate its graph the next time the agent writes to it, or immediately via the Refresh graph button now that the cache is kept in sync.
Changes Since v1.80.0
fix(knowledge): kb_write_page rebuilds the derived graph cache so chat-curated pages/links visualizefix(ui): Knowledge view + KB-selector palette re-fetch the base list (chat-created bases appear without reload)fix(knowledge): brkb::import rewrites the imported manifest id to the deduplicated folder id on collisionfeat(knowledge): kb_export / kb_import MCP tools for .brkb archives
UCSF BioRouter is developed by the Baranzini Lab at the University of California, San Francisco.