Multica
Give each Multica agent its own Mem AI Identity after connecting the AI tool it runs.
Multica can run named agents through local AI tools such as Codex, Claude Code, Pi, OpenCode, or OpenClaw. Connect that AI tool to Nowledge Mem first. Then give each Multica agent one Mem AI Identity.
This means:
- Sessions inside the launched AI tool can sync through that tool's Nowledge Mem connector.
- The Multica agent keeps the same Mem AI Identity when you move it to another workspace or switch the AI tool it uses.
- Multica's own workspace history is separate unless Multica exposes an export, API, or hook for it.
Setup
First connect the AI tool Multica launches. For example, install the Codex, Claude Code, Pi, or OpenClaw connector on the machine running Multica.
Create the Mem AI Identity:
nmem agents upsert cindy \
--name "Cindy" \
--default-space onboarding \
--instructions "Help with onboarding. Explain one step at a time."This creates the Mem AI Identity named Cindy. Its command and environment ID is cindy. It does not make every Codex session use Cindy; the identity is used only where NMEM_AGENT_ID=cindy or agent_id="cindy" is passed.
Then add this custom environment variable to the Multica agent:
NMEM_AGENT_ID=cindyKeep Cindy's ID if she moves to another Multica workspace, squad, or AI tool. Change the connector only when the underlying AI tool changes.
Space
Leave NMEM_SPACE unset unless every task assigned to this Multica agent should use one Mem space:
NMEM_SPACE=onboardingIf the agent works across multiple repos or projects, let the Mem AI Identity's default space handle the usual case and switch space explicitly only when needed.
Security
Do not put broad secrets in Multica agent environment variables. NMEM_AGENT_ID is safe because it is only an identity selector. Mem API keys, provider keys, and production tokens should stay limited in scope and managed through the runtime or Mem client config.