Launching today
Clipnote
Save your AI conversations so they persist after closing tab
99 followers
Save your AI conversations so they persist after closing tab
99 followers
Your ChatGPT and Claude conversations disappear the moment you close the tab. With Clipnote, just tell your AI to "save this" and it's kept on the spot — pasting it in works too, of course. It's a place to keep your AI conversations like a notepad, come back to them later, and pick up right where you left off.
Clipnote
The idea of turning useful AI conversations into something you can actually come back to instead of losing them in endless chat history is quite great. Can Clipnote also organize saved conversations by topic or project?
Clipnote
@yogesh_builds Yes — you can group clips into Collections, so you can organize things by topic, project, or however makes sense to you.
Collections aren't just for organizing, though. You can also make a Collection public, which generates a shareable URL for a "Collection page" — basically a curated index of all the clips inside it. So if you're working through something over multiple AI sessions, you can save each useful bit as you go, then later publish the whole collection as one clean, linkable page instead of sharing a pile of separate links.
@daichi_web Thanks!
Dial
The "save this" via MCP flow is the clever part here, way lower friction than copy-pasting into a separate app. My hesitation is the shareable link piece - a lot of what gets "saved this"-ed out of an AI chat is half-finished or contains something you wouldn't want public by accident. Is there any expiry or access control on those links, or are they permanent and open to anyone with the URL?
Clipnote
@galdayan Good question, and a fair concern.
Links aren't open by default — every clip has a private/public toggle, and anything saved via the MCP flow starts as private automatically. So a "save this" from an AI chat never becomes public unless you explicitly flip it later. No auto-expiry on public links right now, but since publishing is opt-in per clip, there's no scenario where something leaks out just from using the save flow.
On the content side, published HTML is served from a separate domain and rendered in a sandboxed iframe, so even if a clip contains a script, it can't reach your main session or other clips.
Appreciate you flagging it — this is exactly the kind of edge case worth being explicit about on the landing page too.