How Cindy Connects
Cindy is a local agent host. It can run Claude Code, Codex, Pi, and other harnesses while keeping one workspace, memory, skills, and tool surface continuous.
Use Nowledge Mem directly inside Cindy through MCP:
nmem config mcp show --host cindyAdd the generated server in Cindy as nowledge-mem. Then add the shared Mem skills or the Cindy connector guide so the agent knows when to read Working Memory, search prior decisions, save durable lessons, and create handoffs.
Child Runtime Capture
Cindy's built-in agent gets Mem tools through MCP. Exact transcript capture still belongs to the runtime that produced the conversation:
- Cindy-launched Codex: install the Codex connector.
- Cindy-launched Claude Code: install the Claude Code connector.
- Cindy-launched Pi: install the Pi package.
- Cindy-launched OMP: install the OMP plugin.
Keep source_app as codex, claude-code, pi, or the actual child runtime. Use NMEM_AGENT_ID=cindy only when Cindy is a durable role/persona; it is not a replacement for the transcript source.
Current Boundary
Cindy's public client has MCP, shared skills, and a Ghost plugin runtime that can package skills, tools, and a local mcp-stdio worker. That is promising, but Mem does not claim Cindy-native automatic thread sync until a Cindy message export, lifecycle hook, or verified Ghost package install path is stable.
