/check-integration

name: check-integration
description: Check Nowledge Mem setup, detect your agent, and guide native connector setup. Use when the user asks about setup, configuration, or when memory tools aren't working as expected.

Check Connector

> Verify Nowledge Mem is running and guide the user to the best connector for their agent.

When to Use

• User asks about Nowledge Mem setup or configuration
• Memory tools are failing or not available
• User asks "is my memory working?" or "how do I set up Nowledge Mem?"
• First time using Nowledge Mem in this agent
• User asks about upgrading from skills to a native connector

Step 1: Check nmem CLI

nmem --json status

Use this rule before repairing anything:

• **Same machine as Nowledge Mem Desktop:** use the desktop app's bundled `nmem`. Ask the user to open Nowledge Mem; if the command is still missing, use **Settings → Preferences → Developer Tools → Install bundled CLI**.
• **Different machine:** install the standalone PyPI package `nmem-cli` on this machine, then point it at the user's Mem server. This covers remote servers, dev boxes, CI runners, hosted agents, and SSH machines. Python 3.11+ is required.

Do not install the PyPI CLI over the desktop-bundled CLI on the user's own desktop unless the user explicitly asks for a standalone CLI.

If the agent is not on the desktop machine and `nmem` is missing, install the PyPI CLI:

python3 -m pip install --user nmem-cli
# or: pipx install nmem-cli
# or for one-off checks: uvx --from nmem-cli nmem --json status

nmem config client set url https://<their-mem-server>
nmem config client set api-key nmem_...
nmem --json status

If `nmem` exists but status fails, Nowledge Mem is not reachable from this machine. Guide the user:

• Local desktop: open the Nowledge Mem app, then retry `nmem --json status`
• Remote/client machine: verify the URL/API key with `nmem config client show`
• Full install guide: https://mem.nowledge.co/docs/installation
• Remote access guide: https://mem.nowledge.co/docs/remote-access

Step 2: Detect Agent and Recommend The Best Path

For a fresh install, start from the universal connect skill:

Read https://mem.nowledge.co/SKILL.md and follow the instructions to install or update Nowledge Mem for the AI tool I am using.

Use this check-integration skill as the diagnostic fallback: confirm what was installed, explain what behavior the user should expect, and repair configuration when something failed.

Do not only answer "install X". Explain the behavior contract the user will get:

1. what starts automatically 2. what is only guided by skills/rules and still model-driven 3. whether threads are captured automatically, saved explicitly, or only supported as handoff summaries

Use this priority order:

1. **Native connector first** when the host has one 2. **Universal Agent Plugin** when the host supports Agent Plugins but has no native connector 3. **Direct MCP** when the host supports MCP but has no better package path 4. **Reusable package** when the host supports shared skills/prompts but has no native connector, Agent Plugins support, or MCP tool surface

Fresh users care about outcome, not transport. Tell them what they will actually get after setup.

Autonomy levels

| Path | What usually happens | What it does not guarantee | |------|----------------------|----------------------------| | **Native connector** | 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 | | **Universal Agent Plugin** | Standard Agent Plugins package with shared skills plus local Mem MCP for compatible clients without a dedicated connector | Agent Plugins 1.0 does not provide portable lifecycle hooks or transcript access | | **Direct MCP** | Tools are available; with the recommended prompt block, the agent can use them proactively | MCP alone does not create host-enforced autonomy | | **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 |

Check which agent you're running in and recommend the native connector if available.

The canonical source for this table is `community/integrations.json`.

| Agent | How to Detect | Connector setup | Docs | |-------|--------------|----------------------|------| | **Claude Code** | Running as Claude Code agent; `~/.claude/` exists | `claude plugin marketplace add https://github.com/nowledge-co/community && claude plugin install nowledge-mem@nowledge-community` | [Guide](https://mem.nowledge.co/docs/integrations/claude-code) | | **Grok** | Running as Grok; `~/.grok/` exists | `grok plugin install nowledge-co/community#nowledge-mem-claude-code-plugin --trust` | [Guide](https://mem.nowledge.co/docs/integrations/grok) | | **Grok Bot** | Configuring a cloud-hosted Grok Bot; no local CLI installation is expected | Add a custom Nowledge Mem MCP connector in Grok Bot settings with a public HTTPS endpoint. If the Bot or team exposes a compatible Plugins setting, enable the shared package there for supported skills/hooks. Do not use localhost or `127.0.0.1`; automatic full-thread capture still requires a documented Bot transcript export or hook payload. | [Guide](https://mem.nowledge.co/docs/integrations/grok-bot) | | **OpenClaw** | Running as OpenClaw agent; `~/.openclaw/` exists | `openclaw plugins install clawhub:@nowledge/openclaw-nowledge-mem` | [Guide](https://mem.nowledge.co/docs/integrations/openclaw) | | **Cursor** | Running inside Cursor IDE | Copy `nowledge-mem-cursor-plugin` from the community repo into `~/.cursor/plugins/local/nowledge-mem-cursor`, then reload Cursor | [Guide](https://mem.nowledge.co/docs/integrations/cursor) | | **Gemini CLI** | Running as Gemini CLI agent; `~/.gemini/` exists | `gemini extensions install https://github.com/nowledge-co/nowledge-mem-g