Your AI chat is cooked. Uncook it.
No account needed · Private & secure · First time? How to get a share link →
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.
Three steps. No signup.
Open your ChatGPT or Claude chat → Share → Copy link. Drop it in — we pull the whole thing, nothing missed. Not sure how?
Uncook reads the conversation and writes a clean reboot prompt with your decisions and constraints baked in.
Paste it as the first message of a new chat. It picks up cold — no re-explaining, no lost context.
A ready-to-paste reboot prompt — 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.
“I spent two hours building context, then hit the wall. Starting fresh felt like explaining everything to a stranger.”r/ChatGPT user
“It doesn't stop working, it just quietly gets worse. Decisions I'd locked in an hour ago were gone.”Indie founder
“The worst part isn't losing the chat. It's re-typing the same context for the hundredth time.”Consultant, on Reddit
“Past 50 messages it forgets what we agreed on and starts contradicting itself.”r/ClaudeAI user
For anyone whose real work is trapped in a chat that's about to die.
Strategy sessions that run 200 messages deep — don't lose the plan when the chat rots.
Carry a client's whole context into a fresh chat instead of re-briefing the AI every morning.
Keep the brief, the voice and the decisions intact across a week of back-and-forth.
Long document threads that must not drop a clause you settled 80 messages ago.
Restart a study or writing session without losing your outline and sources.
Hand a spec-heavy chat to a clean one before it starts forgetting your constraints.
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.
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, then discarded — never stored, never used for training. Pasted text is analyzed right in your browser.
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.
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.