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.

Install the OMP plugin when you want OMP to start with the right Mem context and save new coding conversations without a manual import step.

After setup, OMP can read Context Bundle or Working Memory at startup, use the bundled memory skills during a task, and sync completed conversation turns into Mem threads with source_app=omp.

Do not install nowledge-mem-pi for OMP. OMP is Pi-derived, but it has its own plugin command, config root, and source tag. The dedicated OMP plugin keeps OMP threads separate from Pi threads.

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

omp plugin install nowledge-mem-omp

Restart OMP after install or update so the extension lifecycle loads.

For most local setups, that is the only OMP-specific install step.

If you also want direct MCP tool calls, or need to point OMP at a custom remote MCP endpoint, generate the optional OMP 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.

Verify

Restart OMP and ask:

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

Success means OMP can see the injected Context Bundle or Working Memory. After you complete a normal OMP turn, the conversation should also appear in Mem as an OMP thread.

Session Capture

New OMP conversations are captured automatically by the plugin after completed agent turns, before compaction, before session switches, and at shutdown. They are saved with source_app=omp.

Only use the sync command when you want to backfill older OMP sessions that existed before the plugin was installed. OMP stores those sessions under ~/.omp/agent/sessions:

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 on the OMP machine and uploads normalized thread messages to your configured Mem server.

Related

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