Mirasim x Nowledge Mem

Mirasim is a local-first multi-agent workbench. Its public docs describe built-in agents, Claude Code and Codex launches, MCP servers, reusable skills, connectors, ui-cli, local session/history commands, and raw recordings.

Nowledge Mem supports Mirasim today through MCP and skills. Native Mirasim transcript sync is intentionally not enabled yet because Mirasim has not published a stable message-level export schema or post-turn hook contract for third-party import.

Setup

Make sure Nowledge Mem is running, then generate the host-specific MCP config from the same nmem client settings you use everywhere else:

nmem status
nmem config mcp show --host mirasim

In Mirasim, add a custom MCP server named nowledge-mem using the generated URL and headers. For local desktop Mem, that points to http://127.0.0.1:14242/mcp/. For Nowledge Cloud, Access Anywhere, or a self-hosted server, the generated block carries the right remote endpoint and authentication shape for your current nmem config.

Then health-check the server from the running Mirasim app:

mirasim ui-cli --port 4970 mcp health --name nowledge-mem

If your Mirasim build accepts GitHub skill sources or Agent Plugins packages, add the shared Nowledge Mem skills from:

https://github.com/nowledge-co/community/tree/main/nowledge-mem-agent-plugin

MCP is the required path. Skills are the behavior layer that teaches the agent when to read Working Memory, search, save durable lessons, and create handoffs.

What You Get

• Working Memory and Context Bundle through Mem MCP
• Memory search and thread search while the agent works
• Durable memory saves for decisions, procedures, and useful debugging lessons
• Library and graph tools when your Mem server exposes them
• Reusable skill guidance inside Mirasim sessions
• Local or remote Mem support through the shared nmem client config

Claude Code And Codex Panes

Mirasim can launch Claude Code and Codex while preserving each tool's own terminal UI and sign-in. Treat those panes as the child tool for transcript capture:

This keeps source_app honest. A Codex transcript launched from Mirasim should still be a Codex thread. Mirasim is the workbench; the child runtime produced the transcript.

Current Thread Sync Boundary

Mirasim documents ui-cli sessions, ui-cli history, and raw model recordings under ~/.mirasim/recordings. Those are useful signals, but they are not enough for a lossless Mem importer until Mirasim exposes one of these:

• a stable message-level export schema,
• a lifecycle hook that can call nmem after a settled turn,
• or a documented API for session transcript reads.

Until then, use handoff summaries from MCP/skills for built-in Mirasim sessions. Do not expect nmem t sync --from mirasim to exist yet.

Troubleshooting

MCP tools do not show up. Run Mirasim's health probe:

mirasim ui-cli --port 4970 mcp health --name nowledge-mem

Mirasim's own troubleshooting guide says a failed MCP handshake can leave an agent without the tools you expected.

nmem config mcp show --host mirasim is unknown. Update the CLI from the same source you installed it:

nmem --version
python3 -m pip install --user --upgrade nmem-cli

If you use the desktop-bundled CLI, reinstall it from Nowledge Mem Settings -> Preferences -> Developer Tools.

Mirasim launched Codex or Claude Code but threads are missing. Install and verify the dedicated connector inside that child tool. The Mirasim MCP server gives memory tools to the built-in Mirasim agent; it does not read Codex or Claude Code transcripts.

Sources

• Mirasim product overview
• Mirasim Skills, MCP and tools
• Mirasim CLI, TUI and ui-cli
• Mirasim Data, recording and privacy
• Mirasim Reference