This issue is AI generated.
Problem
Memory is fully siloed per user. In shared or team deployments (e.g. a family home assistant, a small team's self-hosted instance), there is no way to contribute to or read from a shared knowledge base. Each user's agent learns independently, duplicating effort and missing context that other team members have already established.
Required change
- Introduce an optional shared memory space per NeoAgent instance (or per-group if multi-tenant).
- Allow users to explicitly write memories to the shared space or promote a personal memory to shared.
- Memory retrieval should optionally include the shared space in addition to the personal space.
- Access control: read-all by default for members of a group; write requires explicit user intent (not automatic ingestion).
- Admins can configure which users belong to which group and what the shared space scope is.
Acceptance criteria
- A shared memory space exists and is distinct from any user's personal memory.
- Users can promote a personal memory to the shared space.
- Memory retrieval includes shared entries ranked alongside personal ones.
- Shared memories are clearly labelled in the retrieval inspector.
- Admin can disable the shared space entirely (opt-in deployment feature).
This issue is AI generated.
Problem
Memory is fully siloed per user. In shared or team deployments (e.g. a family home assistant, a small team's self-hosted instance), there is no way to contribute to or read from a shared knowledge base. Each user's agent learns independently, duplicating effort and missing context that other team members have already established.
Required change
Acceptance criteria