Goldfish

Congrats on the launch! I've tried the beta and really like the UI and ambition. I'm curious: what's your own/the team's favorite use cases in everyday work?

Wow, this hits right where it hurts. 🐠The "goldfish memory" of current AI tools is easily the most frustrating part of my daily workflow. I waste so much time copy-pasting Slack threads or brief docs into Claude just to get a relevant reply. Having that context accessible natively with just the ⌥ Option key sounds like a massive productivity unlock.Love the local database approach for privacy too, that's usually the biggest blocker for these kinds of tools.Congrats on the launch Joel!Quick question: how does Goldfish handle context switching? If I move from a client email to a technical dev task, does it easily separate the two "memories" when I press Option?

the context problem is real and underrated. most AI writing tools make you re-explain the situation every single time, which kills the flow. the passive memory angle is interesting, curious how it handles switching between very different work contexts (e.g. a support thread vs a technical doc vs a slack message where tone should be completely different).

wow this product is gold. well done!I do have a few questions on the infrastructure:Is a local model used to generate the replies?How does It formulate a reply in the language (writing style) of the user?Does it only work with what is given on the screen in realtime?

This is so good! Surprisingly works for pretty much any task you could think of, have been using it for the past 3 weeks

It's a smart goldfish that you can talk to and prompt to write messages for you.

crashed my m5 pro laptop today 😭

Hey, Joel. I really appreciate your innovation. I was pleasantly surprised by your project—it’s actually amazing! However, I’m a bit worried about security. Since Goldfish can see everything in every app on my computer, what guarantees do I have that it’s not actually spying on me? For example, when I’m doing something very private, how can I be sure that the info won’t be accessed by Goldfish or even stolen by hackers? Otherwise, I’m really impressed by your creative mind!

The Option key trigger is such a clean wedge. If the reply feels native instead of botty, this could get dangerous fast.

Do you guys have an instagram account?

Love the Option key shortcut, feels so friction less. How does it handle privacy with remembering work across apps? That balance of helpful and private is the hard part to get right. Excited to try it.

I’ve been using Goldfish daily for a month: it’s one of those tools you don’t realize you needed until you can’t imagine working without it. No more copy-pasting Slack threads into a chatbot just to get context. Press Option and it already knows what’s going on.The tone adaptation is the killer feature for me. Writes like me on Slack, like me on email, without any setup. And everything stays local, which matters.Congrats on the launch team 🐠

Well done! Though where I'd get nervous is recall precision:) Once a month of my screen sits in that vector DB, what stops Option from grabbing the wrong thread when two clients have near identical projects open? Overall, solid work!

Huge congrats on the launch 🐠What really lands for me is that Goldfish shows up exactly where the work is happening. I’ve been using it to write and rewrite emails and LinkedIn messages, but also to make sense of complex topics while I’m reading through them at the same time. That cross-app context is the thing that turns AI from a separate chatbot into something genuinely useful in the flow of work.The onboarding was super smooth too, and the local-first memory with explicit privacy controls feels essential for a product that sits this close to messy, sensitive work.Excited to keep using it and see where it goes!

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?