A "Memory Bank" is how Cline works around the fact that it forgets: a memory-bank/ folder of Markdown files (projectbrief, activeContext, progress, …), read back each session to reconstruct context. It's a good pattern — but a file you maintain by hand and reload in full isn't the same as memory that recalls the right fact on its own. This guide covers how the Memory Bank works in Cline, where it breaks, and how to add a real memory layer on top. New to the idea? Start with the complete guide to persistent memory for AI.
How the Memory Bank works in Cline today
Cline is where the Memory Bank pattern was popularised. Because Cline's context is wiped between tasks, it maintains a memory-bank/ folder — projectbrief.md, productContext.md, activeContext.md, systemPatterns.md, techContext.md, progress.md — and re-reads the whole set at the start of every task to reconstruct where it was. It's a clever workaround for statelessness, and for a single repo it genuinely works.
Where the file-based Memory Bank breaks
- Every task re-reads the entire folder, so your context window (and token bill) grows with the Memory Bank — you pay to reload facts you don't need this task.
- The files drift: activeContext.md and progress.md are only as current as the last time Cline remembered to update them, and stale notes quietly mislead the next task.
- It's per-repo and per-machine — clone elsewhere, or open a second project, and the accumulated understanding doesn't come with you.
- There's no retrieval by meaning: Cline reads all of it or none of it, instead of surfacing the one decision that's actually relevant to the question.
The upgrade: a memory layer that recalls by meaning
Before: Cline opens a task by ingesting six Markdown files, most of them irrelevant to what you're doing, and re-derives the rest. After: it recalls only the handful of facts that match the task by meaning, from a store that lives in the cloud — so the context stays small, current, and available on any machine. That's the difference between a static Memory Bank and a real memory layer for AI — a store outside the model that keeps facts and decisions, then surfaces only the relevant ones by meaning.
How to add persistent memory to Cline
- Add the Kit for AI MCP server to Cline's MCP settings with your API key — remember and recall become tools it calls on its own.
- Have Cline recall relevant facts at the start of a task instead of loading the whole memory-bank/ folder, and remember durable decisions and outcomes at the end.
- Keep a namespace per repo so each project's memory stays isolated and clean.
- Leave the Markdown files as short working notes; let the memory layer hold the durable, cross-session recall.
You don't have to choose — do both
Keep the Memory Bank for what it's good at: short working notes and static conventions a human reads too. Add persistent memory for the durable, evolving, cross-session recall the files handle badly. The files stay small; the memory does the remembering. It's also worth knowing that memory and RAG are different jobs — memory persists your decisions, retrieval grounds answers in documents.
FAQ
Does Cline have a built-in Memory Bank?
Cline uses a memory-bank/ folder of Markdown files (projectbrief, activeContext, progress, …) — static files that steer it and give it project context. That's a Memory Bank in the file sense, but it isn't durable, semantic memory: it's maintained by hand, loaded in full each session, and scoped to one repo and machine. A memory layer adds recall by meaning, isolated per project, that follows you across tools.
How do I give Cline persistent memory?
Add the Kit for AI MCP server to Cline with an API key — remember and recall become tools it calls on its own — or use the REST API and SDK where MCP isn't available. It takes a couple of minutes, and the same memory is shared with every other tool you connect.
Related guides
Go deeper: persistent memory for Cline over MCP · add a memory MCP server — or read the pillar on the AI Memory Bank pattern and the guide to persistent memory for AI.
Add real memory to Cline in minutes — Start free, drop in the MCP server with your API key, and remember/recall become tools it calls on its own.