Long AI sessions don’t have a memory problem. They have a memory governance problem. A developer on r/PromptEngineering, u/Street_Witness1328, recently shipped a local browser extension called ZEN LAMP Memory Curator that makes this distinction hard to ignore.
The assumption most people work from is that a good summary of a long AI session is enough to set up the next one. It isn’t. Summaries preserve everything equally. What you actually need is to make a deliberate call: what carries forward, what gets updated, what gets dropped entirely. Getting that wrong is expensive. Not in dollars. In friction, in repeated setup, in carrying outdated assumptions across every new session.
🧠 The real problem with long AI workflows
Every extended AI conversation accumulates context with completely different shelf lives. Fixed rules you’ll always need. Project background that expires at the end of a sprint. A useful insight buried sixty messages in. A temporary workaround you should have dropped three sessions ago. A handoff note meant only for the next chat.
When you summarize all of that into one block, you’re compressing signal and noise together. You carry stale context into new sessions, trip over outdated assumptions, and spend the first twenty minutes of every new chat re-establishing ground the AI should already have.
The author frames this as needing “memory governance,” not just memory. That framing is sharper than it might sound. You’re not trying to preserve everything. You’re deciding what deserves to survive.
ZEN LAMP generates a structured Memory Curator prompt you paste into any AI tool. That AI then helps you sort your context into categories: keep it, update it, drop it, or hand it forward to the next session. The extension contributes the framework. You make the calls. Here’s how the workflow runs:
- Paste your conversation into the extension
- Choose Simple or Power User mode depending on how granular you want the curation
- Choose INITIAL (first-time setup) or UPDATE (refreshing an existing memory block)
- Generate the Memory Curator prompt
- Copy it into your AI of choice and review the structured output
No API calls. No server uploads. No telemetry. The extension generates a text prompt locally and nothing more. Your conversation stays in your browser until you decide what to do with it.
💡 Three things that make this worth your attention
- ⚙️ It works with every AI model you already use. Because the output is a prompt you copy and paste, there’s no lock-in. Claude, ChatGPT, Gemini, or whatever you’re running, they all work. No integrations to configure, no API key to manage, no subscription tied to a specific platform. When the tool you use changes, your memory workflow doesn’t have to.
- 🔄 The UPDATE mode is the part that makes this actually sustainable. First-run memory setup is straightforward enough. The hard part is maintaining that context over weeks or months as your project evolves. UPDATE mode lets you layer in new decisions and prune outdated ones without rebuilding from scratch. Think of it like version control for your working context. That incremental approach is what turns a clever one-time tool into something you’ll still be using in three months.
- 🔒 Privacy here is structural, not a policy promise. There’s no server to receive your data. No background API calls happening while you work. The extension is physically incapable of transmitting your conversation because it never communicates with anything outside your browser. For anyone handling sensitive client context, confidential research, or proprietary workflows, that’s not a minor footnote. Most tools in this space ask you to trust their privacy policy. This one makes the question irrelevant.
🚀 Who gets the most from this
This is particularly well suited for researchers running multi-session threads, writers with projects that span weeks or months, and anyone routinely switching between AI models mid-project. That last case is the most underserved. Moving context from Claude to ChatGPT mid-workflow means rebuilding from scratch unless you have a structured handoff. ZEN LAMP gives you that handoff without depending on any platform to manage it for you. Developers juggling multiple client projects in the same week will feel this immediately too.
I think the “memory governance” framing here is one of the more useful conceptual contributions to show up in AI productivity discussions this year. More memory isn’t the answer. Better decisions about memory are. Those are very different problems and most tools are still solving the first one while this one goes after the second.
The extension is open source, with installation steps and a screenshot in the README. You’ll find the repo link in the original thread on r/PromptEngineering. Worth checking the discussion there too, the use cases people are surfacing are worth reading.
Frequently Asked Questions
Q: Is this just an automatic summarizer?
No. Memory Curator doesn’t compress everything like a typical summarizer. Instead, it helps you actively decide what should be kept, updated, dropped, or carried forward. The goal is intentional memory governance , choosing what matters , not bigger memory by default.
Q: How do INITIAL and UPDATE modes differ?
INITIAL mode creates a memory structure the first time you paste a long conversation. UPDATE mode lets you refresh and evolve an existing memory as you discover new insights or realize old ideas should be dropped. Both help you curate intentionally over time.
Q: If my conversation stays local, how do I use the memory across different AI tools?
The extension generates a copy-paste prompt that you then paste into ChatGPT, Claude, Gemini, or whatever AI tool you’re using next. You review the structured memory output, decide what to keep, and carry it forward wherever you go , you’re always in control.
Q: Why no API calls or server upload?
Keeping everything local protects your privacy (conversations never leave your browser), eliminates API costs, and removes dependency on external services. You get a tool that works offline and puts you in full control of your data.
I built a local Memory Curator extension for long AI chats — no API, no server uploads
by u/Street_Witness1328 in PromptEngineering