One project, many chats
Evenings and weekends are how a lot of projects get built: a college app, a tool for your family's shop, a small game, a site for a local club. AI makes each step faster, and each step tends to get its own chat, sometimes in a different AI.
That's fine while you're in it. The trouble comes later: you come back after a week, open a new chat, and explain the project again from memory, forgetting the one constraint you agreed on.
What a decision log needs
You don't need the whole history. You need:
- What's decided: the stack, the data model, the names, the scope.
- What changed: "we moved from SQLite to Postgres", and why.
- What was set aside: ideas you dropped, so you don't spend another evening on them.
- What doesn't add up: places where two chats say different things.
That last one is the one that bites. Two chats can each be right on their own day and contradict each other a week later.
The chats disagree more than you think.
When you change your mind in one chat, the others don't know. Before you trust any one of them, check it against the others.
Build it by hand
- Open each chat and scroll to the end. The latest decisions are usually near the bottom.
- Copy each decision into one note, with the date and the chat it came from.
- Mark the conflicts: where two chats disagree, note both and decide.
- Keep the note in your project's repository or folder, and update it after each session.
It works, and it's worth doing at least once. With five or six long chats, it takes an evening.
The faster way: Memo, in Uncook
Uncook's Memo reads the chats for you. With the Uncook extension, pick the chats about your project (they can come from different AIs: one in ChatGPT, one in Claude, one in Gemini) and choose Memo. On several chats, you get Where your chats agree, Where they differ, What's still open and an At a glance summary.
On a single long chat, the Memo gives What this is about, What's decided, What was set aside, What changed along the way and What doesn't add up.
Check the account limits in the tool box below. Copy the memo, export it to PDF, Markdown, text or Word, and keep it next to your code.
Carry on in one chat
A memo tells you where you are. To keep building, you want a single chat that knows it too. Uncook's Merge brings the same chats together into one prompt to carry on in one AI. Once you've made the Memo, you can also merge the same chats without sending them again: it counts as 1 more task, shown before you click.
Check the account limits in the tool box below. How it works: merge several ChatGPT conversations into one.
Then keep the memo as your reference, and make a new one when the project moves on.
Questions people ask
Does it work with code? Memo sets out decisions in plain language. Keep your code in your repository: the memo is the note that explains why it looks the way it does.
What if my chats are in different AIs? That's fine. The chats can come from ChatGPT, Claude, Gemini and the other AIs Uncook reads.
Does Uncook keep my project? No. Uncook doesn't keep the chats you bring. The memo is kept as a task, for as long as our Privacy page says.
Start fresh,
without starting over.
Add to Chrome
We don't keep the conversations you bring. When you click Send to Uncook in the extension window, the extension sends the chat from your tab to our servers, encrypted, for up to 30 minutes, and we delete it as soon as your Uncook page opens it. What Uncook makes from it is kept as a task, for as long as our Privacy page says. Neither your chats nor your tasks are used to train AI models.