Multica

Multica runs named agents by starting local AI tools such as Claude Code, Codex, Pi, OpenCode, or OpenClaw. Connect Nowledge Mem at that launched-tool layer, then give each durable Multica agent one Mem AI Identity.

This means:

• Sessions inside the launched AI tool can sync through that tool's Nowledge Mem connector and hooks.
• MCP access must be configured for the Multica agent, not only for the outer terminal you are using.
• 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 the Multica daemon.

If the Multica agent runs Claude Code, also open that Multica agent's MCP settings and save the Nowledge Mem MCP config there. Current Multica merges the runtime machine's native MCP config (for example ~/.claude.json, plus Claude Code plugin MCP servers) with the agent's saved MCP config into one task-local file and forwards it with --mcp-config, so a connector installed on the runtime machine usually rides along already. Saving it on the agent is still the reliable form: agent entries win on name collisions and survive moving the agent to another runtime.

Use the same MCP config you would give Claude Code directly:

{
  "mcpServers": {
    "nowledge-mem": {
      "url": "http://127.0.0.1:14242/mcp/",
      "type": "streamableHttp",
      "headers": {
        "APP": "Claude Code",
        "Authorization": "Bearer <your-nmem-api-key>",
        "X-NMEM-API-Key": "<your-nmem-api-key>"
      }
    }
  }
}

You can generate the exact config for your machine with:

nmem config mcp show --host claude-code --json

For remote Mem, replace the URL with your Access Anywhere MCP endpoint and keep the token headers from your Mem config. Do not put --mcp-config in Multica custom args; current Multica owns that flag and derives it from the agent's MCP config.

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=cindy

Keep Cindy's ID if she moves to another Multica workspace, squad, or AI tool. Change the connector only when the underlying AI tool changes.

What Syncs

New sessions sync only when the launched AI tool has a working Nowledge Mem connector or hook. For example, Claude Code and Codex use their own Nowledge Mem connectors; Pi uses the Pi package; OMP uses the OMP plugin.

Multica itself is the orchestrator. Its issue comments, workspace history, and task timeline are separate data. Multica already exposes run messages through its CLI and API (multica issue runs, multica issue run-messages) and emits task events; Mem does not import those surfaces yet, so today they stay in Multica.

Space

Leave NMEM_SPACE unset unless every task assigned to this Multica agent should use one Mem space:

NMEM_SPACE=onboarding

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

Next

• Customize Connector Behavior
• Lody
• Cumora