Just paste a link — that's the whole setup.
Paste the link to a chat that's worn out. You get back a first message that starts a fresh one exactly where you left off — decisions, constraints, current state.
Uncook reads a public share link — the same link you'd send a friend. Here's the exact tap sequence.
A single-message link (chatgpt.com/s/…) won't work — you need the full-conversation link (chatgpt.com/share/…).
Gemini, Perplexity and Mistral are coming later.
💡 Longer chats get less reliable — that's context rot, and a fresh start is the fix.
Get this handoff by email
Optional — the handoff works fully without an email.
Sent — check your inbox.
Three steps. No signup, nothing to install.
Step 1
Open your ChatGPT or Claude chat → Share → Copy link. Drop it in — we pull the whole thing, nothing missed. Not sure how?
Step 2
Uncook reads the whole conversation and writes a clean Handoff with your decisions and constraints baked in.
Step 3
Paste it as the first message of a new chat. It picks up cold — no re-explaining, no lost context. And if you want, tick “Alert me before my next chat wears out” after your handoff.
A ready-to-paste Handoff — built from your own conversation.
You're my strategic + operational partner on Project Atlas (B2B SaaS, pre-launch). Pick up exactly where we left off. ROOT CONTEXT (non-negotiable) Atlas is a scheduling tool for clinics. ~40 beta users, launch in 3 weeks. The core problem is activation: users sign up but don't connect their calendar, so they never see value. LOCKED DECISIONS · Onboarding leads with calendar connect, before anything else. · Pricing frozen for launch: 1 plan, $29/seat/mo, 14-day trial. · No new features until activation is fixed — one hypothesis at a time. WHAT'S STILL MISSING · Copy for the empty-state that nudges calendar connect. · A metric for "activated" (connected + 1 event booked). MY ROLE: product lead — I decide scope and copy, you draft and pressure-test. Not a designer. WHEN WE RESUME I'll say either "here's the empty-state copy" or "let's define activation." Be direct, no filler. Don't re-ask anything above — it's settled.
Generic example. Your handoff is written from your real conversation — decisions, constraints and current state included.
Same conversation, two other ways out.
Soon you won't even need a share link.
You paste a public share link — the same link you'd send a friend.
ChatGPT: open your chat → click the ⋯ menu at the top-right of the chat title → Share → Create link → Copy. (A single-message chatgpt.com/s/… link won't work; you need chatgpt.com/share/….)
Claude: open your chat → Share → ⚠️ select “Anyone with the link” (required — Claude defaults to a private link Uncook can't read) → Share link → Copy.
Gemini, Perplexity and Mistral are coming later.
ChatGPT won’t create the link (“conversation too long”)? That’s a ChatGPT limit — and exactly the symptom Uncook fixes. Our Chrome extension will capture the conversation straight from your tab, no share link needed — it’s coming. Leave your email to get notified →
A summary is for you to read. A Handoff is for the AI to act on — a ready-to-paste first message that makes a fresh chat resume your work cold, without re-asking what you already settled. That's the part ChatGPT can't do for itself.
No. A share link is fetched once through our server to read the conversation, and its content is sent once to our AI provider (Anthropic) to generate your handoff — then discarded. Never stored, never used for training. If you generate a handoff, a copy also stays in your own browser (on your device only, never sent to us) for 24 hours, so a reload doesn't lose it — clearing it removes it immediately.
ChatGPT and Claude share links today. Gemini, Perplexity and Mistral coming later — reach out if you'd like them supported sooner.
No signup, no card. Paste a link, get your handoff.
Yes — after your handoff, tick “Alert me before my next chat wears out” and leave your email. Separate, optional opt-in: one-click unsubscribe in every email, and your address is deleted the moment you leave.
Every AI has a limited context window. As a chat fills up it starts dropping early details, repeating itself and forgetting rules you set. A clean restart with the right context fixes it.