Persistent memory for Claude Code, Cursor & Copilot
Your project's decisions, context and tasks, shared by every AI tool and every teammate, and flagged when the code moves on.
Claude already remembers you. It doesn't remember your project, and it never reaches Cursor or your team. Here's the difference
Save to ContextForge: no automatic retries on the payment webhook, they double-charged customers. This webhook fails sometimes. Should I add a retry? No. Your project memory says retries on this webhook double-charged customers.
Each tool remembers only itself
Claude, Cursor and Copilot each keep some memory now, but it stays inside that one tool and that one account.
Claude Code
This decision stays here.
Cursor
› Should I add a retry?
Yes, I'll add a retry.
This double-charges customers.
GitHub Copilot
› Should I add a retry?
Yes, adding retries now.
This double-charges customers.
ContextForge keeps one memory for every tool and teammate. See how it works
One memory. Every tool.
Connect the tools you already use. They all read and write the same project memory.
What your agents can do with it
Plain tools your agent calls on its own.
See what else is running.
Check which other Claude Code sessions are live before a big change.
Keeps the to-do list.
Tasks stay with the project, not in one chat.
Saves the why.
Decisions keep their reason, so the next agent does not undo them.
- Spaces
- Separate memory per repo, service or team.
- Snapshots
- Point-in-time copies you can restore or diff.
- Team
- Shared spaces with per-member roles.
- Import / Export
- Move memory in and out as JSON or Markdown.
- API keys
- Scoped keys for CI and your own scripts.
Tutorials
See how it works
Short walkthroughs of the features people ask about most. Watch the video or skim the article.
How to Stop Claude Code From Losing Context (2026)
Yesterday I was in the middle of a release with Claude Code. Two hours in, the session hit the context limit and compacted itself. In the old days that was t...
7 min read
Claude Code Compaction: Why Your Session Forgets Mid-Task (and the Fix)
Last week I published a piece about handing off a Claude Code session without re-explaining everything. A reader left a comment that stuck with me: "Compacti...
6 min read
VideoGive Your AI Coding Agent a Memory That Survives Every Session
Give Your AI Coding Agent a Memory That Survives Every Session Open a new session with Claude Code, Cursor, or Copilot and it has no idea what you were doing...
2 min read
VideoSkills Were Dead Prompts. Routines Made Them Alive.
A few weeks ago I shipped Skills — a way to save AI prompts as reusable templates inside ContextForge , so my best prompts wouldn't keep dying in a Notion pa...
6 min read
VideoI Built Skills Because My Notes App Was Full of Dead Prompts
Open your Notes app right now. Search "prompt." Count what comes up. If you're anything like the 200+ developers I've talked to in the last six months, the a...
7 min read
Import Your AI Memory into ContextForge: Claude Code, ChatGPT, and Knowledge Graph
You've been building knowledge with your AI assistant for months — project decisions, API patterns, debugging notes. But that knowledge is scattered acro...
2 min read
GitHub Copilot Now Supports MCP — Here's How to Give It Persistent Memory
GitHub Copilot just got MCP support. That means you can now connect external tools directly to Copilot's Agent Mode in VS Code. One thing you can do with...
3 min read
ContextForge Now Supports Cursor IDE: Persistent AI Memory Everywhere
{"time":1773257511919,"blocks":[{"id":"9ge_aeLB75","type":"paragraph","data":{"text":"If you've ever wished your AI coding assistant could remember things be...
2 min read
How to Give Claude Persistent Memory with MCP
Every conversation with Claude starts from zero. It doesn't remember the stack you chose last week, the naming conventions you prefer, or the bug you spent t...
5 min read
Simple pricing
Per month. Cancel any time.