Connect with the Product Hunt community

To demo Explain s power we present to you Reddit TV (redditwatch.tv) which automagically creates short videos of any Reddit post, summarising the discussion. The homepage pulls in Reddit's most popular posts which refresh every 15 minutes and you can also use the search field to tune into the most popular posts from any subreddit (subreddit feeds refresh once per day).  These explainer videos are generated on-the-fly within seconds the first time someone clicks a post and we cache them for instant playback for the next viewer  .

YC applications close in 11 days...

And every day I find one more thing I want to fix before submitting.

When PH was in its early days, upvotes were the most important. (They are still in demand now), but people increasingly want comments.

Because PH no longer counts only upvotes in the final ranking, but also other things: upvoting, commenting, sharing, etc.

In August, Ross and I bought N8N Chat UI from its original creator. He'd built something brilliant: the widget, streaming, voice, file uploads and the JavaScript API were all his work. Our job was to take it further and get it in front of more people.

What we've learned in the 12 weeks since:

You inherit decisions you didn't make. Pricing, free tiers, naming. Some of it we kept, and some we're still working out. It's humbling to defend a choice you'd never have made yourself, then find out why it was made.

Plugins open more doors than features do. Our first big step was meeting people where they already are: WordPress, Wix, Webflow and an n8n community node. Most people don't want an embed snippet. They want a button in the tool they already use.

Me and Raf have been working together for more than 12 years !

He was the founder of the animation studio where I joined as an intern.

Purchasing a product has many different angles of decisions, from understanding the brand, figuring out if the product is worth it, and ultimately deciding if the price is right.
A lot of it comes down to the relationship the prospect has with the site, which is where N8N Chat UI comes into play - Allowing you to make modules as dynamic as you want, or as tame as you want.
We've just launched on ProductHunt, link is here https://www.producthunt.com/prod...

Most websites lose almost everyone who visits. People land, have a question or a doubt, don't find the answer quickly, and leave. A chat widget is the obvious fix, but one that sits in the corner waiting to be clicked usually doesn't do much.
What we've seen work better, working with agencies and shop owners, is treating chat as part of the sales process, not a support add-on:

1. Show up at the right moment. Open the widget when someone's been on the checkout page for a couple of minutes, or sat on a product page without adding anything to the cart. That's usually when a question is stopping the sale (delivery, returns, sizing).

2. Know why they're there. Pass the page, the product or the cart to your n8n workflow with every message, so the agent can answer the actual question and doesn't open with "How can I help?".

3. Ask different questions on different pages. Pricing-page prompts and returns-page prompts shouldn't be the same.

4. Don't lose the people who aren't ready to buy. Capture them as leads into your CRM (HubSpot, Pipedrive, Mailchimp or whatever you use) with consent, so you can follow up.

5. Book the calls. Let the chat book the meeting with Calendly or Cal.com, so a warm visitor doesn't have to wait for an email.

All of that can be wired up with n8n and a bit of JavaScript, and we've put ready-made workflows for the CRM, booking and order-lookup parts at n8nchatui.com/recipes.
What I'd like to know: which of these has actually moved the needle for you or your clients? And what have you tried that didn't work? I'd love real numbers if anyone's willing to share.

iKnowMyMac 1.7 is out, free for every license. What's new:

• Blocking, off until you turn it on: block any connection by app, domain or country, for 5 minutes, an hour or always

• Install Guard and Agent Guard: hold a connection when an install script or a coding agent reaches somewhere new, and explain it before you decide

• A map of where your connections go, 12 months of history per app with a privacy score, tracker and malware blocklists, encrypted DNS

• A Traffic Control window from the menu bar ( T)

What would you block first?

Full notes: https://iknowmymac.com/changelog

Gabriel and I both open the repo in the morning and kind of... hope for the best hehe

Sometimes we're on the same file without knowing it.

That's literally the problem we're trying to fix with Murmell, a multiplayer workspace for coding with AI.

But the human side is still messy :)

When someone asks for a feature, it's tempting to assume they've already identified the solution to their problem.

But sometimes the request is only one possible way to solve something deeper.

For example, a customer might ask for another dashboard when what they're really struggling with is knowing which information deserves their attention.

I can see two approaches.

A percentage says what's gone. A Lancetta suggestion says what to do about it, and shows the numbers it rests on so you can weigh it. No model is asked: it's plain arithmetic on your Mac.

Slow down: "At this pace Claude stops in 51m, then waits 1h18m for its reset." Both moments, because the gap between them is the time you'd lose.

I came across this question in the YC application:

Please tell us about the time you most successfully hacked some (non-computer) system to your advantage.

A few days ago I asked if you track how much you spend on AI...

The answers were gold hehe

I started out tracking what new launches on Product Hunt, Hacker News and PeerPush were built with. I had developers in mind when I built it.

Then I started finding websites beyond the launch boards. Shops, salons, trades, cafes, agencies. Businesses putting their sites live without posting about it anywhere.

AI assistants already work on my Mac. They start dev servers, run builds, and when something is slow, they try to find out why.

All they see is a thousand process names, so they guess. And when they clean up, they can't tell a dev server I forgot last week from the database I'm working in.

Today I have an interview at our national radio station, where I ll be answering questions about myself, RunEvr, and our animation studio.

So let s warm up here first =D

I m a co-founder of RunEvr - an agentic environment for creative teams.

I have 12+ years in animation production, working across almost every stage - from creative work and art direction to a production manager.

A few people asked here how Many Displays tells identical monitors apart, especially behind a dock, so I wrote it up properly. It covers why macOS mixes them up (same EDID serial plus the DisplayPort disconnect on sleep), a Terminal command to see what your own monitors report, and the clues that can still tell them apart: system UUID, physical port, manufacture date and position.
https://manydisplays.com/identic...
If you run the command and your two monitors print the same serial, I'd love to hear what setup you have.

Solving a real problem isn't always enough if the user has to consciously remember to log in every time.

We had a tool that worked brilliantly on paper but because it wasn't tied to a daily trigger people completely forgot about it after a few days.

How do you cross the line from a useful utility app into something people open every single day without thinking?

Hi, it's Morse. Thanks for following AgentValley. Since the launch on Saturday I put out 5 small updates, and two of them came from people here and on GitHub.

1. Leo Heo asked if the card could show how long an agent has been waiting, so he could answer the oldest one first. Now there is a red badge next to "needs you" with the time, and the bar in the notch shows the longest wait after a minute.

2. DJ Sipe asked to use it on a bigger screen next to his MacBook. You can pick the screen in Settings > General > Display. If you unplug it, it goes back to the notch.

3. If you have a lot of sessions open, the ALL page now folds them to one line each when they don't fit, so your other project stays on screen. A session that needs you never folds.

4. Sounds are on by default now. Settings > Sounds turns them off.

5. The app should ask you to update on its own, or run brew upgrade --cask agent-valley.

One thing I want to know: if you run more than 3 or 4 sessions at once, does the folding help or get in the way?

We're taking part in the GPT-6 Astra Challenge with OpenAI right now, which got me thinking about this.

New models drop constantly. Some people test everything immediately, others stick with what works until there's a real reason to switch.

I'm three weeks from launch and I have a list of fourteen things I could still build. I know I can't build all of them. What I don't have is a rule for deciding.

The rule I've been using "cut anything that isn't core" is useless, because everything feels core when you're the one who built it.

What I'm trying to get to is a single non-negotiable: the one thing that, if it's missing, the product isn't the product. Everything else is a candidate for cutting.

So for the solo makers here: what was your one non-negotiable thing at launch, and what did you cut that you thought you couldn't? And looking back, did cutting it hurt, or did nobody notice?

Apart from featuring in the Product Hunt newsletter and some awareness.
What measurable (long-term) outcomes did you get?

E.g. apart from increased traffic it could be:
XY long-term users
 collaboration claimed
investors who gave you XY amount of money

Share your highlights that stemmed from the ranking.

Hi everyone

Thanks for all the support on Taste Lab. A lot of you used it to pull the visual DNA out of websites you love.

But I kept running into the next problem. Even with the right visual style, an AI-built page can still feel off, because the agent doesn't know what belongs on the page, in what order, or why.

We're applying with Murmell one more time hehe

Got rejected last batch.

It's funny watching teams panic over model safety guards while their container network policies are wide open. If an agent manages to probe internal services or reach outside connections, it s not because the model got "too smart" it s because the isolation layer was poorly built from day one.

Prompt tuning won't save a leaky environment. How does your team usually test your container boundaries before shipping?