Proma × Nowledge Mem

Read https://mem.nowledge.co/SKILL.md and follow the instructions to install or update Nowledge Mem for Proma. Verify with nmem status, startup context, and a saved Proma thread, then summarize what changed.

Proma can use Nowledge Mem in three ways:

• MCP tools let Proma search memories, save durable knowledge, and browse Mem when the task needs it.
• Lifecycle hooks save Proma conversations into Mem threads.
• Startup context writes your current Mem context into Proma's workspace CLAUDE.md, so new Proma sessions begin with the right memory.

Proma v0.13.0 and newer include a Nowledge Mem card in Proma's Memory settings. Start there if you are setting this up for the first time: it copies a setup prompt you can paste into Proma Agent mode. Keep this page open for the exact files, update steps, and verification checks.

Before You Start

• Nowledge Mem is running locally, or you have a reachable remote Mem server.
• Proma is installed.
• Python 3.9+ is available as python3.
• nmem works in your terminal.

nmem status

If nmem is missing, install it from the Mem desktop app developer tools or run:

pip install nmem-cli

Install

If you are on Proma v0.13.0 or newer, open Proma Settings → Memory → Nowledge Mem, copy the setup prompt, and paste it into Proma Agent mode. The manual steps below are the same contract, written out so you can audit or repair the setup.

The examples use Proma's default workspace. If your workspace has a different name, replace default with the directory name under ~/.proma/agent-workspaces/. If your platform exposes Python only as python, replace python3 with python in the hook commands.

rm -rf /tmp/nowledge-community
git clone https://github.com/nowledge-co/community.git /tmp/nowledge-community

mkdir -p ~/.proma/scripts ~/.proma/agent-workspaces/default/skills
cp /tmp/nowledge-community/nowledge-mem-proma-plugin/hooks/save-to-nmem.py ~/.proma/scripts/
cp /tmp/nowledge-community/nowledge-mem-proma-plugin/hooks/read-working-memory.py ~/.proma/scripts/
chmod +x ~/.proma/scripts/save-to-nmem.py ~/.proma/scripts/read-working-memory.py
cp -R /tmp/nowledge-community/nowledge-mem-proma-plugin/skills/{read-working-memory,search-memory,distill-memory,save-thread,status} ~/.proma/agent-workspaces/default/skills/

~/.proma/agent-workspaces/default/mcp.json

{
  "servers": {
    "nowledge-mem": {
      "url": "http://127.0.0.1:14242/mcp/",
      "type": "streamableHttp",
      "headers": {
        "APP": "Proma"
      }
    }
  }
}

{
  "servers": {
    "nowledge-mem": {
      "url": "https://mem.example.com/mcp/",
      "type": "streamableHttp",
      "headers": {
        "APP": "Proma",
        "Authorization": "Bearer nmem_your_key",
        "X-NMEM-API-Key": "nmem_your_key"
      }
    }
  }
}

~/.proma/sdk-config/.claude/settings.json

{
  "hooks": {
    "SessionStart": [
      {
        "matcher": "startup|resume",
        "hooks": [
          {
            "type": "command",
            "command": "python3 \"$HOME/.proma/scripts/read-working-memory.py\"",
            "timeout": 15000
          }
        ]
      }
    ],
    "UserPromptSubmit": [
      {
        "hooks": [
          {
            "type": "command",
            "command": "python3 \"$HOME/.proma/scripts/save-to-nmem.py\" --event user-prompt-submit",
            "timeout": 30000
          }
        ]
      }
    ],
    "Stop": [
      {
        "hooks": [
          {
            "type": "command",
            "command": "python3 \"$HOME/.proma/scripts/save-to-nmem.py\" --event stop",
            "timeout": 30000
          }
        ]
      },
      {
        "hooks": [
          {
            "type": "command",
            "command": "python3 \"$HOME/.proma/scripts/read-working-memory.py\" --rewake",
            "timeout": 15000,
            "async": true,
            "asyncRewake": true,
            "rewakeMessage": "Nowledge Mem context refreshed"
          }
        ]
      }
    ]
  }
}

What Happens

• UserPromptSubmit saves the current Proma thread before the next user turn.
• Stop saves again after a response, so missed or delayed transcript writes are covered.
• The save hook reads Proma transcripts from ~/.proma/sdk-config/projects/**/<session-id>.jsonl and writes them as source proma.
• SessionStart refreshes the Nowledge Mem block inside ~/.proma/agent-workspaces/default/CLAUDE.md.
• Stop asyncRewake can push a compact Working Memory reminder after assistant turns.

Proma's current Claude Agent SDK does not reliably inject SessionStart stdout as model context. That is why this connector writes a marked CLAUDE.md block instead:

<!-- nowledge-mem:start -->
...
<!-- nowledge-mem:end -->

Keep your own Proma instructions outside that block, or in CLAUDE.md.template.

Update

cd /tmp/nowledge-community
git pull

cp nowledge-mem-proma-plugin/hooks/save-to-nmem.py ~/.proma/scripts/
cp nowledge-mem-proma-plugin/hooks/read-working-memory.py ~/.proma/scripts/
chmod +x ~/.proma/scripts/save-to-nmem.py ~/.proma/scripts/read-working-memory.py
cp -R nowledge-mem-proma-plugin/skills/{read-working-memory,search-memory,distill-memory,save-thread,status} ~/.proma/agent-workspaces/default/skills/

Then merge the latest nowledge-mem-proma-plugin/hooks/hooks.json into ~/.proma/sdk-config/.claude/settings.json and restart Proma.

Remote Mode

For MCP, keep the remote URL and key in Proma's mcp.json.

For hooks and CLI fallback, configure the local nmem client once on the machine running Proma:

nmem config client set url https://mem.example.com
nmem config client set api-key nmem_your_key

Troubleshooting

MCP tools do not appear. Confirm mcp.json uses servers as the top-level key, then restart Proma.

Startup context does not appear. Run python ~/.proma/scripts/read-working-memory.py, then check ~/.proma/agent-workspaces/default/CLAUDE.md for the nowledge-mem:start block.

Threads do not appear in Mem. Wait for Proma to finish a turn, then check ~/.proma/logs/nm-hooks.log and search with nmem t search "<phrase>" --source proma.

Remote MCP works, but hooks do not. MCP uses Proma's mcp.json; hooks use the local nmem client config. Set both to the same remote Mem server.

Related

• Connectors overview
• Claude Code
• Remote access