cd /news/ai-agents/how-to-give-cursor-memory-between-se… · home › topics › ai-agents › article
[ARTICLE · art-174175] src=nestdaddy.com ↗ pub= topic=ai-agents verified=true sentiment=· neutral

How to give Cursor memory between sessions

NestDaddy Memory, an MCP server from NestDaddy, is being promoted as a way to give Cursor's agent persistent memory across sessions by letting it save, semantically recall and replace project decisions, with setup requiring a free month at nestdaddy.com/memory and adding the remote MCP endpoint https://nestdaddy.com/memory/mcp in Cursor's settings. The vendor says the same memory is shared across Claude, ChatGPT, VS Code and Windsurf, and recommends adding a user rule instructing the agent to call recall before tasks, save_memory on decisions and log_turn after each answer. The pitch targets Cursor's session-to-session amnesia, which rules files in .cursor/rules only partly address because they hold only hand-written context.

key takeaway

Connecting the NestDaddy Memory MCP server at https://nestdaddy.com/memory/mcp and adding a user rule to call recall before each task, save_memory on decisions and log_turn after answers lets Cursor's agent carry decisions across sessions instead of re-reading the codebase.

read3 min views2 publishedNov 22, 2026
How to give Cursor memory between sessions
Image: Nestdaddy (auto-discovered)

Cursor forgets your architecture, your decisions and yesterday's task every time you open a new chat. Rules files help, but they only hold what you write by hand. Here is how to give Cursor a real memory that it reads and writes itself, shared with every other AI you use.

You spent the afternoon with Cursor's agent on a refactor. You agreed on the folder layout, picked a library and stopped halfway through the migration. Next morning you open a new chat and type "continue the migration". The agent starts reading the codebase from scratch, and suggests the library you rejected yesterday.

Cursor is brilliant inside one session. Between sessions it forgets.

What Cursor remembers today #

  • Rules files. Project rules (in.cursor/rules ) and user rules are added to the agent's context. They are great for stable things: code style, the stack, "always write tests".
  • The codebase itself. The agent can search and read your files every time.

What neither of them holds: decisions and why you made them, what you did yesterday, what you tried that failed, and anything from your other AI apps. Rules only contain what you type by hand, and nobody updates a rules file after every session.

A memory the agent writes itself #

NestDaddy Memory is an MCP server. Once it is connected, Cursor's agent can:

  • save decisions as you make them ("we use Postgres, because orders and stock need one transaction"),
  • find them by meaning in any later session, even when you word things differently,
  • replace a decision when you change your mind, so the old plan never comes back,
  • look back in time : "what did we change last week?" gets a day-by-day answer,
  • find past conversations : "continue yesterday's work" finds where you stopped.

And because it is one memory for every AI you use, what you decided in Claude or ChatGPT this morning is there in Cursor this afternoon.

Connect it to Cursor #

  1. Start your free month at nestdaddy.com/memory . No card.
  2. In Cursor, open Settings and findMCP (under Tools in recent versions).
  3. Add a new MCP server. Choose the remote or HTTP type, name it nestdaddy-memory and use this address:https://nestdaddy.com/memory/mcp
  4. Your browser opens a NestDaddy page. Sign in and click Allow . No keys to copy.

The same steps work in VS Code, Windsurf and other editors that support remote MCP servers.

Make the agent use it every session #

Add one line to your user rules (or a project rule), so the agent checks memory before it starts:

My main memory is the NestDaddy Memory MCP server. On every task, first call recall with my request, and search it before you decide anything about this project. When we decide something, save it with save_memory. After each answer, log the turn with log_turn.

Now try it. Tell the agent: "Remember that we chose Postgres for this project, because orders and stock need one transaction." Open a new chat tomorrow and ask: "Which database did we pick, and why?"

Why not just a markdown file? #

A memory.md in the repo is a fine start. It breaks down when:

  • it grows past what fits in context, so the agent stops reading it all,
  • two decisions disagree and the agent cannot tell which one is newer,
  • you want it in Claude, ChatGPT or on your phone, not only in this repo.

NestDaddy Memory handles those for you: search by meaning instead of reading everything, the latest decision always wins with full history kept, and one memory across every AI and device.

Start today #

Every session you work without memory is context you will explain again. Start your AI's memory today, and let your agent pick up exactly where you left off: nestdaddy.com/memory.

── more in #ai-agents 4 stories · sorted by recency
── more on @nestdaddy 3 stories trending now
sponsored brought to you by zahid.host 4,200+ EU-deployed projects
reading about agents? ship yours in a single git push.

Run your AI side-project on zahid.host

EU-based hosting, git-push deploys, automatic HTTPS, no cold starts. Free tier with a custom domain — perfect for shipping the agent you just read about.

$git push zahid main
→ Live at https://your-agent.zahid.host ✓
Get free account → Pricing
from €0/mo · no card required
LIVE [news/how-to-give-cursor-m…] indexed:0 read:3min 2026-11-22 · —