Problem
Memmy is local-first, which is valuable, but currently the practical experience is still centered around the computer where the Memory Service and database are running.
For users with multiple computers, this creates a major limitation:
- Memories created on one computer are not automatically available on another.
- Each computer may end up with an independent and incomplete memory database.
- Agents running on different devices cannot reliably share the same context.
- Moving or copying the local database manually is not a practical synchronization solution.
Feature request
Please add a first-class self-hosted memory hub mode.
The intended setup would be:
- Run one Memmy Memory Service on an always-on computer, home server, NAS, or private cloud server.
- Treat that instance as the single source of truth for memories.
- Connect Codex, Claude Code, Memmy Desktop, CLI clients, and other supported agents from multiple devices to the same instance.
- Authenticate each client using a secure URL and access token.
- Allow all connected devices to search, add, and update the same memory collection.
Memmy already exposes some of the underlying remote connection options, but this workflow should become an officially supported and documented product mode rather than requiring users to assemble the setup themselves.
Suggested scope
A complete remote hub mode could include:
- A documented server deployment process
- Docker or Docker Compose deployment
- Configuration through the Desktop app, not only CLI flags
- Server URL and API token settings for client devices
- Token creation, revocation, and rotation
- Secure defaults and HTTPS or reverse-proxy guidance
- Support for concurrent access from multiple clients
- Clear behavior when a client temporarily loses its connection
- Health checks and connection diagnostics
- Backup and restore instructions
- Guidance for migrating an existing local memory database to the hub
Expected outcome
A user should be able to run one private Memmy instance as their personal memory center and securely access the same memories from every computer and agent they use.
The data would remain under the user's control while no longer being limited to a single device.
Related: #1
Problem
Memmy is local-first, which is valuable, but currently the practical experience is still centered around the computer where the Memory Service and database are running.
For users with multiple computers, this creates a major limitation:
Feature request
Please add a first-class self-hosted memory hub mode.
The intended setup would be:
Memmy already exposes some of the underlying remote connection options, but this workflow should become an officially supported and documented product mode rather than requiring users to assemble the setup themselves.
Suggested scope
A complete remote hub mode could include:
Expected outcome
A user should be able to run one private Memmy instance as their personal memory center and securely access the same memories from every computer and agent they use.
The data would remain under the user's control while no longer being limited to a single device.
Related: #1