-
Notifications
You must be signed in to change notification settings - Fork 156
Hi,
I’ve been reading Bub’s code and wanted to understand the intended direction around memory.
From what I can tell, tape is persisted and keyed by workspace + session_id, so Bub supports continuity when the same session is reused. But it does not seem to provide built-in cross-session memory by default.
Curious whether there’s any roadmap or early thinking around this already? Is cross-session / long-term memory something Bub is expected to support more directly over time? Or is the current session-scoped tape model intended to remain the main abstraction?
I’m asking mainly to understand whether this is aligned with Bub’s design goals before experimenting further. Thanks.
All reactions
-
❤️ 1
Replies: 1 comment 2 replies
Sorry for the late reply.
For me, a typical use case is this: if tape A and tape B were created by the same bub instance, that bub can see all the information. So I often use it in my personal session to troubleshoot specific issues within the group seesion.
Handling cross-session within the same Bub is not difficult, but what about another Bub? One effective approach currently is to use a database; this way, we don’t need to worry about how to expose the tape externally, and we only need to manage which Bub tenants have permission to read data from other Bub instances.
There are some diagrams at https://tape.systems/; I think the sections on Teams and access control might be helpful.
All reactions
-
❤️ 1
As for the non-tape portion, regarding memory, I think you can check out @wey-gu 's nowledge-mem; there's a Bub plugin that implements this. https://github.com/nowledge-co/community/tree/main/nowledge-mem-bub-plugin
All reactions
-
❤️ 1 -
👀 1
Thanks for the pointer, I will check it out