Launching today
Most AI tools make you explain the context before they can help. Goldfish already has it. It privately remembers what you’ve been working on across your Mac, then helps you write better from any app. Press Option in a text field to draft replies, summarize threads, rewrite sentences, or recall important details from your recent work without copying, pasting, or re-explaining the whole backstory.









Hey Product Hunt 👋 Joel here, one of the two Swedish founders building Goldfish.
Why we built it:
We started building Goldfish because AI still has one weird problem: it knows the internet, but not the work sitting right in front of you. AI has memory like a goldfish!
Your messages, docs, tabs, meetings, half-written drafts, people, decisions, and loose threads already live on your computer. But every time you open a chatbot, you start from zero again. You paste the thread, explain the project, describe the person, and try to make it sound like you.
That felt backwards to us.
What Goldfish is:
Goldfish is a private AI memory layer for your Mac. It understands what you’re working on across apps, then lets you use that context anywhere you type.
Press ⌥ Option in any text field and Goldfish can help you:
write replies in your own tone, with the thread and relationship context already there
summarize messy work from Slack, Gmail, docs, tabs, or meetings
recall things you saw, wrote, read, or discussed
rewrite highlighted text without touching the rest
bring your full computer context into Claude Desktop through our local MCP server
What we believe:
The best AI product won’t be another empty chat box.
It will be the memory layer underneath your work. Something that understands your context privately, shows up where you already are, and removes the need to re-explain yourself 50 times a day.
Early traction:
We’ve worked closely with 1,000+ founding members to build a product people can’t live without. GTM people at ElevenLabs, Deel, and Vercel are already using Goldfish to write faster replies in their own tone.
Our founding team comes from Strawberry Browser (General Catalyst) and Depict (YC20), and we’re currently building from The Bridge by Entrepreneur First in San Francisco.
Privacy:
Privacy is core to the product. Your memory stays on your Mac in a local database. No cloud sync, no backend where we can browse your data, and you can stop capture of apps and domains any time. AI calls have zero data retention.
Product Hunt offer:
Goldfish is still in closed beta, but we’re opening early access to the Product Hunt community first.
As a thank you, everyone from Product Hunt gets 3 months of free access!!
Download now at goldfish.sh
We’d love feedback on:
where it feels magical
where it gets context wrong
what more you’d want goldfish to do in the future
Thanks for checking us out 🐠
This is one of the more interesting AI products I’ve seen here recently.
The part that resonates most is the “starting from zero every time” problem. As a founder, I constantly switch between product decisions, emails, support, launch copy, team messages, and random notes. Most AI tools are useful, but only after I spend time explaining the context again. 😅
The privacy approach is also important here. A product like this only works if users can actually trust it with messy, unfinished, sometimes sensitive work! :)
Curious how much control users have over what Goldfish remembers or ignores. Can I exclude specific apps, websites, projects, or time periods from memory?
@andrasczeizel You can control it pretty tightly. You can pause capture whenever you want, and exclude specific apps or domains so they never get remembered.
The memory lives locally on your Mac, and you can delete stored history too. We built it assuming people will have messy, sensitive work on screen, so “what should Goldfish ignore?” is a core part of the product, not an afterthought! :-)
Our real power users are mostly founders, so I would love for you to try it! lmk if you have any feedback! :)
@andrasczeizel yes, exactly. You can exclude specific apps and websites from memory, and pause capture whenever you want. Is app/site level enough for control, or would you want something more granular? We are working on a way to dynamically distinct between "personal" and "work" context
The "knows your work" part is where these tools either actually deliver or fall apart.
Curious what that means concretely here: are you indexing local files, pulling from open apps, reading browser tabs, or something else? And how does it handle context switching across very different types of work, like if I'm mid-deep-work on a coding problem and then get a Slack message about a completely separate client project, does it actually pick the right context or does it need a nudge?
@fberrez1 Hey Florent! Yeah so we're using the built in accessibility API:s to get the text content currently visible on the screen, and that is enough to get enough context about what you're working on. We store that on a local database and in a vector database. It tracks the sort of work you do across different surfaces and remembers what belongs to where, so that it adapts to your tone in different projects.
Feel free to try it out and let me know what you love and what you hate! It would be super useful to get some feedback! :)
this is very very cool, just tried it! :)
is it able to change the tone of your reply to say your grandmother vs your best friend?
@armaan_nagra Happy to hear that you like it, Armaan! :)
Yes, it knows the tone of you depending on in what context and who you're responding to. One user told us it understood even a certain dialect of a language where she only wrote in that dialect with family members, so hopefully it understands enough.
@armaan_nagra yes, it also stores memory about how your tone changes between different apps and sites! What apps do you think you'll use it most for?
@joel_edholm linkedin haha, i need to clear my inbox
The Option-key workflow feels smart because it keeps AI inside the place you’re already writing. Curious how Goldfish decides which recent context should matter and which old context should fade out.
@farrukh_butt1 Very good question! We keep a buffer of the most recent-recent context which gets embedded with each option-click, but when it makes sense Goldfish can also search way back into the long term memory, but often the most recent memory is enough.
Have you tried it yet? What do you think? :)
SocialBu
Congrats on the launch, Joel! The 'starting from zero every time' problem with AI is incredibly real—I waste so much time re-pasting Slack threads and briefs. Keeping the memory layer local via SQLite/vector DB is a massive win for trust. Quick question: How does it impact Mac performance or battery life when it's actively indexing active apps?
@bilal_niaz I feel you, we had the same problem before goldfish existed! Yes indeed - local first is a winner in our opinion :)!
It doesn't affect performance too much, we utilize the already existing accessibility APIs to get the text from open windows, which is super lightweight. We also run an optimized model for doing embeddings as not to tax the computer unnecessarily much.
Have you given goldfish a try yet? Best way to assess performance also! :- D
Wow gonna give this a try. Are the memories local?
@alexander_gusev3 Happy to hear that Alexander!
Yes, so everything is saved in a local sqlite database and a vector database! Let me know when you've tried it and if you have any feedback 🙏☺️
@alexander_gusev3 yes, fully local. Nobody can see your data, not even us the creators!