OMP × Nowledge Mem

Read https://mem.nowledge.co/SKILL.md and follow the instructions to install or update Nowledge Mem for OMP. Verify with nmem status and the Context Bundle or Working Memory check, then summarize what changed.

OMP is Pi-derived and supports MCP, skills, and runtime extensions. Use MCP plus skills for live memory tools, and use nmem t sync --from omp when you want OMP's local session files imported into Mem.

Before You Start

• Nowledge Mem is running locally, or you have a reachable remote Mem server
• OMP is installed
• nmem works on the same machine as OMP

nmem status

Setup

Generate the MCP config:

nmem config mcp show --host omp

Add the generated server to OMP's MCP config. OMP's documented MCP locations include project .omp/mcp.json and user ~/.omp/agent/mcp.json. Then import the Nowledge Mem skills into OMP.

Verify

Restart OMP and ask:

Read my Nowledge Mem context and tell me whether the connection is working.

Success means OMP can call the Nowledge Mem MCP tools and return Context Bundle, Working Memory, or a clean empty result.

Session Capture

OMP stores sessions under ~/.omp/agent/sessions. Import them with:

nmem t sync --from omp --limit 20
nmem t sync --from omp --apply

This works for local Mem and remote Mem because nmem reads the local OMP JSONL files and uploads normalized thread messages to your configured Mem server.

This is not a live hook package yet. OMP exposes Pi-like extension lifecycle events, so a native package is the right next step for automatic capture. Until then, use the import command after important sessions and ask OMP to save handoff summaries when you need an immediate curated checkpoint.

Related

• Pi
• OpenCode · Kimi Code · ZCode
• OMP docs: omp.sh/docs