Skip to main content
Connectors
Orchestrator

Cumora

AI teammate setup: connect the AI tool Cumora launches, then give each teammate its own Mem AI Identity instruction.

Cumora GuideOpen Cumora

Start with the setup prompt or connection guide. Open the guide for detailed steps.

Agent shortcut

Ask your agent to set it up

Copy the setup prompt. Your agent will open this guide, use the recommended path, and verify the setup.

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:

TEXT 
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.

More Orchestrator Connectors

Raft
Raft

Connect memory to each Raft worker without mistaking its managed Codex execution trace for the human conversation.

By Nowledge Labs
Raft GuideOpen Raft
Lody

Runtime launcher setup: connect the AI tool Lody launches, then add a Mem AI Identity only when an Agent Config represents a stable role.

By Nowledge Labs
Lody GuideOpen Lody
Multica
Multica

Multi-agent setup: connect the AI tool Multica launches, add its MCP config when needed, then give each Multica agent one Mem AI Identity.

By Nowledge Labs
Multica GuideOpen Multica