Summary
This PR adds the first Robrix UI layer for octos-backed persistent knowledge scopes:
- room-scoped memory
- space-scoped knowledge bank
It builds on the existing Matrix appservice + BotFather integration and makes persistent bot context visible and editable from the client.
What Changed
- added a client-facing representation of room memory
- added a client-facing representation of space knowledge bank state
- exposed memory/knowledge controls through Robrix UI
- kept room-scoped and space-scoped knowledge isolated
- preserved existing BotFather and appservice room binding behavior
Why
Robrix already lets users bind BotFather to a room and create/manage bots, but it does not yet expose the persistent knowledge that drives long-running bot usefulness.
This PR closes that gap by letting users manage:
- room-local bot context
- shared space-level knowledge reused across related rooms
Result
Users can now treat Robrix as the front end for both bot routing and bot knowledge management, instead of relying on hidden backend-only memory state.
Notes
This PR focuses on the first usable knowledge-management layer.
It does not introduce:
- voice workflows
- thread session/task routing
- skill/package management UX
Summary
This PR adds the first Robrix UI layer for octos-backed persistent knowledge scopes:
It builds on the existing Matrix appservice + BotFather integration and makes persistent bot context visible and editable from the client.
What Changed
Why
Robrix already lets users bind BotFather to a room and create/manage bots, but it does not yet expose the persistent knowledge that drives long-running bot usefulness.
This PR closes that gap by letting users manage:
Result
Users can now treat Robrix as the front end for both bot routing and bot knowledge management, instead of relying on hidden backend-only memory state.
Notes
This PR focuses on the first usable knowledge-management layer.
It does not introduce: