How Cumora Connects
Cumora is a teammate workspace, so the ideal Mem boundary is one Mem AI Identity per durable Cumora teammate.
Connect the AI tool Cumora launches first. Sessions inside that tool can sync through that tool's Nowledge Mem connector. If Cumora does not expose per-agent environment variables, add a short persona instruction instead:
Nowledge Mem:
- Read Context Bundle as agent_id="atlas" at task start.
- Use host_agent_id="cumora:atlas" when supported.
- Pass agent_id="atlas" again on later memory search/save/thread calls.
Use per-agent NMEM_AGENT_ID only when Cumora exposes real per-agent environment variables. Do not set one shared daemon identity for several teammates. Cumora-native rooms and internal Cumora memory need a Cumora export, API, or hook before Mem can import them directly.