Repository navigation
Idea: hosted namespace standing behind the local hub for cross-machine sync #547
Description
Hi, I found memmy-agent while mapping the local memory hub space, and giving Claude Code, Codex, OpenClaw, and Hermes one shared memory is exactly the right product instinct.
The gap a local hub hits in practice is the same memory living across machines, devices, or a second teammate, where sync and backup become the project.
I run BlueColumn, a hosted memory API with per-key namespaces and native audio ingestion. I would be glad to send a working code example of a hosted namespace standing behind the local hub. Would that be interesting as an optional sync backend?
Activity
dolnna commentedon Oct 9, 2026
Thanks for writing this up, and for calling out the cross-machine / teammate gap. That matches where we're headed.
Cross-device memory and multi-person collaboration are already on our roadmap. The collaboration side is planned as privacy-preserving sharing between teammates' assistants, rather than an external hosted namespace sitting behind the local hub.
We're building that as part of Memmy, so we aren't looking for an optional third-party sync backend right now. Appreciate you offering the example anyway.