Skip to main content
Nowledge MemNowledge Mem

Persistent memory for Cursor

Connect Cursor to Nowledge Mem to reuse saved context across agent sessions. Start with the local plugin and verify memory search.

For your agent

Give this line to your agent. It should use the universal install skill first; this page remains the behavior and troubleshooting reference:

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

Recommended today: local plugin install

The most reliable path today is local install from ~/.cursor/plugins/local/nowledge-mem-cursor. It works before Marketplace acceptance and uses the same package you would later publish.

Marketplace is optional later

If Nowledge Mem eventually becomes visible in Cursor Marketplace for your account, you can switch to that path later. The local package path below is the user-ready path now.

The practical benefit is simple: install once, start a new agent session, and Cursor gets the rule, skills, hook, and MCP wiring together.

Before You Start

  • Nowledge Mem running locally (installation) or a reachable remote Mem server
  • Cursor IDE installed
  • Recommended: nmem in your PATH if you want automatic Context Bundle / Working Memory bootstrap and resumable handoff creation through the terminal tool

If Nowledge Mem is already running on the same machine through the desktop app, the easiest path is Settings → Preferences → Developer Tools → Install CLI. That gives Cursor access to nmem for session-start Context Bundle / Working Memory bootstrap and explicit handoff creation.

For real Cursor Agent thread history, Mem reads Cursor's local Agent transcript files from ~/.cursor/projects. The desktop app can auto-sync them on the same machine. For a deliberate backfill, preview first:

nmem t sync --from cursor --all-projects

Then import after you confirm the list:

nmem t sync --from cursor --all-projects --apply

If you only want one project, point at its transcript folder:

nmem t sync --from cursor --session-dir ~/.cursor/projects/Users-me-project/agent-transcripts --apply

One-Minute Setup

Clone or open the package folder

git clone https://github.com/nowledge-co/community.git
cd community

Copy the plugin into Cursor's local plugin folder

mkdir -p ~/.cursor/plugins/local
rm -rf ~/.cursor/plugins/local/nowledge-mem-cursor
cp -R nowledge-mem-cursor-plugin ~/.cursor/plugins/local/nowledge-mem-cursor

If you want faster local iteration, you can try a symlink instead:

ln -s "$(pwd)/nowledge-mem-cursor-plugin" ~/.cursor/plugins/local/nowledge-mem-cursor

Cursor staff have confirmed that local plugin symlink resolution is currently buggy in practice, so copy-first is the reliable path.

Reload Cursor

Restart Cursor or run Developer: Reload Window.

If Cursor still shows Claude Code wording or an older plugin id, remove the older imported nowledge-mem package from Cursor first. This package exposes a sessionStart hook for startup context and a stop hook for automatic transcript capture, in addition to the Nowledge Mem skills. The local plugin id is nowledge-mem-cursor specifically to avoid colliding with that imported package.

Start a new agent session

For the default same-machine setup, the bundled plugin assets are the intended zero-config path:

  • plugin manifest
  • rule
  • skills
  • session-start hook
  • local mcp.json

If nmem is installed, the session-start hook can preload Working Memory into the new Cursor session before the agent begins.

Configure MCP for remote Mem only

Only if you use remote Mem, open Settings (Cmd/Ctrl+Shift+J) -> Features -> Model Context Protocol and update the nowledge-mem server URL and headers.

If you also want the sessionStart hook and save-handoff skill to work against remote Mem, point the local nmem client at the same remote server:

nmem config client set url https://your-server
nmem config client set api-key your-key

The split is intentional:

  • Cursor MCP settings drive the plugin's memory tools
  • nmem config client ... drives the terminal-side bootstrap and handoff flow on this machine

Update

If you installed through the local plugin folder:

  • recommended copied path: replace ~/.cursor/plugins/local/nowledge-mem-cursor with a fresh copy, then reload Cursor
  • optional symlink path: pull the latest community changes and reload Cursor, but switch back to copied install if Cursor stops detecting the plugin

If Marketplace support appears later, you can uninstall the local copy and move to Marketplace.

Customize Safely

Use Cursor's own rule files for behavior changes:

  • .cursor/rules/*.mdc
  • .cursorrules

Keep the packaged Nowledge Mem rule as the default. Do not patch the installed plugin files under ~/.cursor/plugins/.... Full map: Customize Integration Behavior.

Your First Success State

You know the plugin is set up correctly when:

  • the plugin is installed from ~/.cursor/plugins/local/nowledge-mem-cursor
  • you start a new Cursor agent session
  • if nmem is installed, Working Memory is already available at the start of the session
  • same-machine setup works without hand-editing MCP config
  • in remote mode, updating the nowledge-mem MCP server is enough to restore the same behavior
  • Cursor is not showing a stale Claude-oriented package surface such as save-thread, beforeSubmitPrompt, or stop

What You Get

  • Bundled .cursor-plugin/plugin.json
  • Bundled hooks/hooks.json with a sessionStart Context Bundle / Working Memory bootstrap
  • Bundled mcp.json for local Nowledge Mem MCP connectivity
  • An always-on rule for Working Memory, routed recall, distillation, and handoff semantics
  • Four skills: read-working-memory, search-memory, distill-memory, and save-handoff
  • Real Cursor Agent transcript import through Mem desktop auto-sync or nmem t sync --from cursor

What Users Usually Care About

For a fresh install, the important answers are simple:

  • local Mem: install the plugin and start a new session
  • remote Mem: install the plugin, then update the nowledge-mem MCP server URL and headers; if you want bootstrap and handoff too, also point nmem at the same remote server
  • best Cursor experience: keep nmem installed so the session-start hook can preload Working Memory and Cursor can create handoff summaries when needed

Important Constraint

The package includes save-thread as an explicit fallback and save-handoff for a concise resumable summary.

Its stop hook captures the current Cursor Agent transcript automatically when Cursor provides the transcript path. Mem desktop and nmem t sync --from cursor remain available for historical or missed sessions; both paths read Cursor's local agent-transcripts JSONL files and append deduplicated messages into Mem.

Package Shape

This package is already arranged in Cursor's plugin format:

.cursor-plugin/plugin.json
rules/nowledge-mem.mdc
skills/*/SKILL.md
hooks/hooks.json
hooks/session-start.mjs
mcp.json

Cursor's local plugin folder expects .cursor-plugin/plugin.json at the package root. This package already matches that contract, so the local install path above is stable and direct.

Marketplace Later

If Cursor Marketplace accepts the package later, install Nowledge Mem there and keep the same behavior. Until then, the local plugin folder is the right path for users.

On this page