// Check Nowledge Mem setup, detect your agent, and guide native plugin installation. Use when the user asks about setup, configuration, or when memory tools aren't working as expected.
| name | check-integration |
| description | Check Nowledge Mem setup, detect your agent, and guide native plugin installation. Use when the user asks about setup, configuration, or when memory tools aren't working as expected. |
Verify Nowledge Mem is running and guide the user to the best integration for their agent.
nmem --json status
If this fails, Nowledge Mem is not installed or not running. Guide the user:
Do not only answer "install X". Explain the behavior contract the user will get:
Use this priority order:
Fresh users care about outcome, not transport. Tell them what they will actually get after setup.
| Path | What usually happens | What it does not guarantee |
|---|---|---|
| Native integration | Strongest setup: session bootstrap is often automatic; some hosts also add auto-capture or hook-driven recall | Exact proactive recall/distill timing can still be host-specific |
| Reusable package | Working Memory, recall, and distill are guided by rules/skills | The host may still ignore the guidance unless prompts and project guidance are strong |
| Direct MCP | Tools are available; with the recommended prompt block, the agent can use them proactively | MCP alone does not create host-enforced autonomy |
Check which agent you're running in and recommend the native plugin if available.
The canonical source for this table is community/integrations.json.
| Agent | How to Detect | Native Plugin Install | Docs |
|---|---|---|---|
| Claude Code | Running as Claude Code agent; ~/.claude/ exists | claude plugin marketplace add nowledge-co/community && claude plugin install nowledge-mem@nowledge-community | Guide |
| OpenClaw | Running as OpenClaw agent; ~/.openclaw/ exists | openclaw plugins install clawhub:@nowledge/openclaw-nowledge-mem | Guide |
| Cursor | Running inside Cursor IDE | Link nowledge-mem-cursor-plugin into ~/.cursor/plugins/local/nowledge-mem-cursor, then reload Cursor | Guide |
| Gemini CLI | Running as Gemini CLI agent; ~/.gemini/ exists | Search "Nowledge Mem" in the Gemini CLI Extensions Gallery | Guide |
| Alma | Running inside Alma; ~/.config/alma/ exists | In Alma: Settings > Plugins > Marketplace, search "Nowledge Mem" | Guide |
| Droid | Running inside Droid (Factory) | Add nowledge-co/community marketplace, install nowledge-mem@nowledge-community | Guide |
| Codex CLI | Running as Codex CLI agent; ~/.codex/ exists | codex plugin marketplace add nowledge-co/community (legacy fallback: codex marketplace add nowledge-co/community), install nowledge-mem@nowledge-community from /plugins, enable [features] plugins = true, hooks = true, plugin_hooks = true, and [plugins."nowledge-mem@nowledge-community"] enabled = true, then run the installed scripts/install_hooks.py once for automatic thread capture. Add mcp_servers.nowledge-mem only when overriding the bundled local MCP endpoint. | Guide |
| Bub | Running inside Bub | pip install nowledge-mem-bub | Guide |
| Pi | Running as Pi agent; ~/.pi/ exists | pi install npm:nowledge-mem-pi | Guide |
| OpenCode | Running as OpenCode agent; ~/.config/opencode/ or .opencode/ exists | Add "opencode-nowledge-mem" to opencode.json plugin array | Guide |
| Hermes Agent | Running as Hermes agent; ~/.hermes/ exists | Install the native Hermes provider (or use MCP only as fallback) | Guide |
If the agent is not listed above:
npx skills package when the host supports itDo not describe raw MCP as equivalent to a native integration.
After setup, verify with:
nmem --json m search "test" -n 1
If this returns results (or an empty list with no error), the integration is working.
Then state the expected outcome in plain language:
If the path is only guided, say what strengthens it:
nmem available locallyAGENTS.md or equivalent repo guidance when recommendednmem client in remote modeSkills give you CLI-based memory access. Native plugins usually add:
/remember, /recall, /forget (where supported)Do not promise all of these on every host. Match the actual path the user is setting up.
Save durable Nowledge Mem insights when a Proma conversation produces decisions, procedures, preferences, plans, learnings, or project context that should survive future sessions.
Load the Nowledge Mem Working Memory briefing at Proma session start, after a break, or when recent context would help the current task.
Save or archive the current Proma session to Nowledge Mem when the user explicitly asks, especially as a fallback when automatic hooks are unavailable.
Search Nowledge Mem memories and threads from Proma when the user references past work, prior decisions, recurring problems, or project history.
Check whether Nowledge Mem is reachable from Proma, including MCP status, CLI fallback, API URL, and configuration issues after install or update.
Search past decisions, procedures, learnings, or context relevant to the current task. Trigger when work connects to prior decisions, a debugging pattern resembles a past issue, the user asks about rationale, or uses recall language like "that approach" or "like before".