Cumora

Cumora is an AI teammate workspace. Its agents have personas, can start conversations, and may carry their own internal memory.

Nowledge Mem should not replace that. It should give each Cumora teammate access to the same durable, cross-tool knowledge layer the user already shares with Codex, Claude Code, Pi, OpenClaw, browsers, notes, and the Library.

The important rule: do not give a shared computer-level daemon one NMEM_AGENT_ID if several Cumora teammates use it. If Atlas, Iris, Bram, and Nova all inherit the same daemon identity, Mem will treat them as one teammate. That is worse than leaving identity unset.

Best Current Path

Use a two-step setup:

1. Connect the AI coding tool Cumora launches.
2. Add a small Mem AI Identity instruction to each Cumora agent persona.

This works even when Cumora gives you only one local npx or daemon command per computer, because the identity is selected by the agent's instruction, not by the daemon's environment.

Connect The Runtime

Install and verify Nowledge Mem on the computer where Cumora starts the AI tool:

nmem status

Then connect the tool Cumora launches, such as Codex or Claude Code:

• Codex
• Claude Code
• Pi

This gives that tool access to Mem tools, Context Bundle / Working Memory, and any session-sync hooks it supports. For example, if Cumora launches Codex or Claude Code and those connectors are installed, those tool sessions can sync through their Nowledge Mem hooks.

Add The Persona Bridge

For each long-lived Cumora teammate, create a Mem AI Identity:

nmem agents upsert atlas \
  --name "Atlas" \
  --default-space research \
  --instructions "Research across the user's knowledge. Cite sources and separate facts from interpretation."

Atlas is the display name. atlas is the stable id. This command only creates the identity record; it is used when the Cumora persona passes agent_id="atlas" or when a future per-agent environment sets NMEM_AGENT_ID=atlas.

Then add this short block to that Cumora agent's persona or system prompt:

Nowledge Mem:
- At the start of a task, read Context Bundle as agent_id="atlas".
- If the tool supports it, also pass host_agent_id="cumora:atlas".
- Keep source_app as the AI tool when known, such as "codex" or "claude-code".
- For later Nowledge Mem calls, pass agent_id="atlas" again so memory_search, thread_search, read_working_memory, and memory_add use the same identity and default space.
- Save durable decisions, preferences, and procedures when they matter beyond this conversation.

If the agent only has CLI access, the same behavior is:

nmem --json context --agent-id atlas --host-agent-id cumora:atlas --source-app codex

Use the returned active space for later commands:

nmem --json m search "recent research decisions" --space research
nmem --json m add "Atlas learned that ..." -t "Research note" --space research -s codex

If the agent has MCP access, prefer passing agent_id directly:

read_context_bundle(agent_id="atlas", source_app="codex", host_agent_id="cumora:atlas")
read_working_memory(agent_id="atlas", source_app="codex", host_agent_id="cumora:atlas")
memory_search(query="recent research decisions", agent_id="atlas", source_app="codex")
thread_search(query="last onboarding discussion", agent_id="atlas", source_app="codex")
memory_add(content="Atlas learned that ...", title="Research note", agent_id="atlas", source_app="codex")

This is the clean fallback until Cumora exposes per-agent environment variables or an official integration point.

If Cumora Adds Per-Agent Env

If Cumora later lets each agent set environment variables, move the identity out of the persona prompt and into that per-agent environment:

NMEM_AGENT_ID=atlas
NMEM_HOST_AGENT_ID=cumora:atlas

Do not set these on the shared daemon unless that daemon belongs to exactly one Cumora teammate.

What Syncs

Supported AI-tool sessions can sync. If Cumora launches Codex, Claude Code, Pi, OpenClaw, or another tool with a Nowledge Mem connector, use that connector's normal sync path.

Cumora-native history is different. Nowledge Mem cannot directly import Cumora rooms or Cumora's internal agent memory unless Cumora exposes a local API, export, hook, or per-agent runtime integration point.

Until then, Cumora's own internal memory stays inside Cumora. Nowledge Mem remains the user's cross-tool, cross-agent knowledge layer for the connected AI tools, saved memories, notes, and Library.

Next

• Customize Connector Behavior
• Slock
• Multica