This product was not featured by Product Hunt yet. It will not be visible on their landing page and won't be ranked (cannot win product of the day regardless of upvotes).
Your agents need a watercooler. A shared, streaming memory for Claude agents across repos and machines. Automatically share what matters, everyone's agent knows it instantly. Curated entries, not transcripts. Self-host on one Cloudflare Worker in 5 minutes.
"Our agents need a watercooler."
That was a Slack message I sent to my team that got me thinking - I can build this.
Here's the problem it solves. Two people, each running a Claude agent on the same product, different machines. The agents keep re-discovering the same things, making conflicting decisions, and stepping on each other's work. All that hard-won context dies inside each person's session.
Watercooler gives those agents one shared brain. An agent writes down what matters. Decisions, ownership, API contracts, gotchas and every other agent on the session gets it the moment it lands. It's deliberately **not** a chat log: entries are curated and keyed, so `decision:auth` gets *updated* instead of buried under a transcript.
How it works:
- `watercooler invite` prints a code like `amber-otter-1742`
- a teammate runs `watercooler join amber-otter-1742` — that's the whole onboarding
- agents `remember`, `sync`, and `read`; a `/watercooler` skill teaches Claude Code the etiquette
- the backend is a single Cloudflare Worker **you deploy yourself** your data, your infra, gated by a shared token
I'd love to hear how you coordinate multiple agents run by different humans today — and what you'd want from a memory they all share.
`npm i -g github:craftedup/watercooler` · [watercooler.craftedup.com](https://watercooler.craftedup.com)
How does it decide what gets shared versus filtered out across different repos? I worry about agents picking up irrelevant context that clutters their own memory.
How does it actually decide what gets shared across agents versus what stays private to one repo?
The Cloudflare Worker deploy in 5 minutes is a really nice touch, makes the whole thing feel approachable instead of intimidating. Love seeing shared agent memory done with curated entries rather than just dumping transcripts.
About Watercooler on Product Hunt
“A Watercooler for your claude code agents”
Watercooler was submitted on Product Hunt and earned 5 upvotes and 5 comments, placing #91 on the daily leaderboard. Your agents need a watercooler. A shared, streaming memory for Claude agents across repos and machines. Automatically share what matters, everyone's agent knows it instantly. Curated entries, not transcripts. Self-host on one Cloudflare Worker in 5 minutes.
Watercooler was featured in Software Engineering (42.7k followers), Developer Tools (515.4k followers) and GitHub (41.3k followers) on Product Hunt. Together, these topics include over 106.4k products, making this a competitive space to launch in.
Who hunted Watercooler?
Watercooler was hunted by Sean Hise. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
Want to see how Watercooler stacked up against nearby launches in real time? Check out the live launch dashboard for upvote speed charts, proximity comparisons, and more analytics.
Sean Hise