Every new ChatGPT chat starts from zero. You spend two hours mapping out a plan, the chat gets too long to continue, and all of it disappears. That’s the exact wall u/Ok_Negotiation_2587 hit on r/ChatGPTPromptGenius, and the fix that got 40 upvotes needs one prompt, nothing installed.
Memory sometimes surfaces a piece of the old conversation, sure. But you can’t choose which piece it keeps, and it’s almost never the piece you actually need.
The Key Idea
Here’s the swap that fixes it: stop asking ChatGPT for “a summary.” Ask it for a briefing written for a reader who has no memory of the conversation at all.
That one change in wording matters more than it sounds. A summary condenses. A briefing explains, because it assumes the reader knows nothing. Every obvious part has to be spelled out, not just the tricky bits.
Quick start: paste one prompt into your old chat, copy what comes back into a new chat with a short prefix, then keep working. That’s the whole method, and it works on any chat that’s gotten too long to continue.
Old Way vs New Way
The old way is copying random chunks of the old chat into the new one and hoping the important part made the cut. Or leaning on ChatGPT’s memory feature, which stores bits it picked, not the bits you’d pick.
The new way is generating a proper handoff document first, then feeding it in as labeled context. Here’s the exact prompt the original poster uses in the old chat:
Summarize everything we decided in this conversation as a briefing for a new chat that has no memory of it. Include the goal, the decisions made, the constraints, anything still open, and the exact wording of any final text we agreed on. Skip the back and forth.
Why it works: telling the model who its reader is changes what it optimizes for. “No memory of it” forces the model to write context instead of compressing it. It also has to preserve exact wording on anything you already locked in, instead of paraphrasing it into mush.
Practical Steps
- Go to the old chat and send the briefing prompt above, word for word.
- Copy the full answer it gives you.
- Open a new chat and start your message with “Context from a previous conversation:” then paste the briefing.
- Right after that, write what you actually want done.
A commenter on the thread pointed out a simpler variant for ongoing work. Ask the model to write documentation as you go, in the first chat. Then the new chat has something built already, instead of a one-time summary.
For the automated version, the original poster built this into a browser extension called AI Toolbox to skip the copy-paste dance. Type “@@” in the composer and pick a past chat from the list. Its content gets inserted, pasted whole if short, summarized if long, with the rest of your prompt right after it. The free plan allows 3 uses a day, the paid plan lifts the cap, and it works the same across ChatGPT, Claude, Gemini, and Grok.
Three prompt combos worth stealing once you have context loaded in, whether by hand or with “@@”:
- Using the plan in [old chat], write the first draft of the launch email.
- Compare what we decided in [chat A] against [chat B] and list every contradiction.
- Continue the coding session in [old chat] from where we stopped, same conventions.
One warning worth noting: this only works as well as the briefing prompt itself. Asking for a “recap” or a “TLDR” instead will hand you back a squashed version that skips exactly the details you needed.
Once you’ve run it a couple of times, try the JSON variant a commenter suggested. Add a line asking the model to export the briefing “in the most optimized machine-readable form in a code block.” It reads worse to a human, but it pastes into a new chat just as cleanly. It also keeps structure that plain text tends to lose.
The original poster ended the post with an open question worth sitting with. Some people keep one giant master chat for everything instead of splitting work across sessions. That approach skips the handoff problem entirely. But it trades that problem for a different one: a chat so long the model starts losing track of the middle of it.
Try the manual version on your next stalled chat before you install anything. If it saves you the two hours of re-explaining, head over to the original thread and see how other people are running it. The JSON export trick and the “write docs as you go” approach are both buried in the comments.
Frequently Asked Questions
Q: What’s the difference between this and just writing documentation as I go?
Some users prefer asking the AI to write documentation incrementally during the initial chat, then referencing that in the new chat. Both approaches solve the same problem, it just depends on your workflow. The briefing method is more intentional and structured; the documentation-as-you-go method embeds context naturally as decisions are made.
Q: Can I export the briefing in a structured format like JSON?
Yes. You can modify the request to ask the AI to “export the information in the most optimized machine-readable form in a code block,” which typically generates JSON. This is useful if you want to store, organize, or parse the context programmatically.
Q: Does this technique work with Claude, Gemini, and other models?
Absolutely. The core technique (asking for a briefing) works with any chat model. The manual copy-paste method is completely free and model-agnostic. The AI Toolbox extension supports ChatGPT, Claude, Gemini, and Grok.
Q: When should I create a briefing instead of continuing in the same chat?
Create a briefing when your chat is getting long (hitting response lag or token limits), or when you’re about to take a break and won’t continue immediately. Also useful when multiple people or agents need to pick up where you left off.
The prompt technique that fixed my biggest ChatGPT annoyance: every new chat starts from zero
by u/Ok_Negotiation_2587 in ChatGPTPromptGenius