Setting up AgentMemory on a remote server as centralized memory service

[Rex57]

@rohitg00 I’m running AgentMemory on a remote server as a centralized
memory service for my team. Multiple clients connect to the same server
through the REST/MCP setup.

I wanted to ask whether there are plans to make this workflow more
native/easier for team use. A few things we are trying to handle:

1. Multiple users/clients working against the same shared AgentMemory
   server.

2. Each user/client having a distinct identity, so memories and sessions
   can still show who created them.

3. Multiple local checkouts of the same repo mapping to the same project
   in AgentMemory.

The main issue is project/session naming. Different team members may
have the same repo in different paths or folder names, so AgentMemory
can treat them as different projects even though they are the same
codebase.

Right now we are solving this by setting a per-repo env var with direnv:

AGENTMEMORY_PROJECT_NAME=our-shared-project-name

This works, but it requires every client to configure the same value
manually for each repo.

Is there any plan or recommended approach for this use case? For
example, something like deriving the project name from the Git remote/
repo name, or a native team/shared-project config so all clients
automatically map to the same AgentMemory project while still keeping
distinct user IDs.