Connect with the Product Hunt community

Everyone talks about launch day. The upvotes. The ranking. The traffic spike.

But for me the best moment is quieter than that. It's when a stranger uses something you built and it just works for them. No help needed. No DM asking how. They just got value out of it and moved on with their day.

Email opens are no longer the benchmark, now it's all about conversions.

Why do you send email?

Quick backstory on the "why": octoscope's repo drill-in shows a 12-month star-history sparkline, and that reads GitHub's stargazers endpoint which GitHub has been tightening (a scoped token is now required) and which throws the odd 5xx. The catch: one failed star-history call used to abort the whole detail view. Not great.

Now it's best-effort. If star history can't load, octoscope just drops the sparkline and still shows the description, license, latest release, recent commits and open issues/PRs. The star count itself was never affected that's a public number, not the restricted list.

We just raised $100M here's what we're building

Hey everyone! TwelveLabs just closed a $100M Series B and wanted to share what we're working on for anyone who hasn't come across us before.

We're a video AI company. The core problem we're solving: video is the richest record of reality we have, but machines still can't really understand it. Most systems just convert footage to text and call it a day. We think that's leaving a lot on the table.

Our platform has two main models:

VibeAround v0.7.17 is out.

This release focuses on a deceptively hard problem: when the same local coding-agent session is accessible from Web, TUI, and messaging channels, every surface needs to agree on what active, queued, stopped, and finished mean.

If you get unlimited access to the best models with Fable and sol, what's the most ambitious thing you'd build?
Also, where would you use these models to build things? In Claude, some other harness?

When we first built Murror's AI companion, we did what every AI product does -- we made it ask a lot of questions.

"How does that make you feel?"

"Can you tell me more about that?"

We just hit 30 days worth of signups in a SINGLE day.

1M+ people saw us in today s Product Hunt newsletter, and Jesse is officially becoming a sales household name (an officehold, if you will ).

A year ago, writing code was most of my day.

Today I spend much more time reviewing AI output, refining prompts, validating behavior, making product decisions, and connecting pieces together.

Hey Product Hunt,

Hey all. I'm really interested in how you evaluate your agents in production.

The standard approach is sample, LLM as judge and possibly a golden dataset. That seems to be the standard setup.

I keep seeing the same pattern in product launches: "Now with AI!" slapped on everything like a magic label.

But here's what I've noticed from watching dozens of AI-powered products succeed and fail:

Yes, it's been a long time coming! ... but launch day is upon us.

Anyone who's ever walked the halls of indie-development knows that no product ever feels ready to show. Even now, the list of in-development improvements and features is so long that tomorrow's relaunch here on Product Hunt just feels wrong.
... but if we never do it, we never do it.

Hey everyone! Tomorrow, Wednesday June 10, we're launching Publora on Product Hunt, and we're equal parts excited and nervous. I'm sure many of you know this pre-launch feeling full of hopes and a little bit of stress

This past year has been a turning point for us. Publora started out as a social media scheduler now it's an MCP server. In practice that means your AI agent (Claude Code, Cursor, Antigravity, whatever you use) can handle social for you: read your feed, comment on posts in your space, react to mentions that matter, reply to messages. You just talk to your agent in plain language and it happens. No new UI to learn, no manual cross-posting.

To celebrate, we've got a little something for the PH community: use code PH20THANKU for 20% off your first payment.

Every maker hits the same wall. You ship a feature, users have questions, and you end up copy pasting the same answers across email, Discord, and Twitter DMs all day. That s hours you should be spending on the product itself. This is exactly why I built Lyqn AI. It learns your product, answers instantly, and never sleeps. No more repeating yourself. No more support tickets piling up while you re trying to ship. The part I m most proud of is the WhatsApp bridge. A user can start chatting on your website, then continue the exact same conversation on WhatsApp without losing context. Most people don t live in your chat widget. They live in WhatsApp. So your support should follow them there. If you re running a product and drowning in repetitive support questions, this is for you. Check it out and tell me what s missing. Building this in public, so every bit of feedback shapes what comes next.

Hey everyone, posting today's release notes.

Most of what shipped is in three places: what generated drafts are allowed to do, the Compose screen, and navigation.

Hey PH

I spent the last week doing the heavy lifting of researching the best prompts across LinkedIn and Reddit and testing them for marketing, social media, strategy, and image generation to see what actually works versus what s just hype.

Hey Product Hunt

We re still processing today.

We ended up as the #2 Product of the Day, and we also got featured, right alongside some incredible products we genuinely admire like @Framer . Seeing @Swytchcode sit there still doesn t feel fully real.

We're back on Product Hunt, and we've been busy

Last time we launched, you made us Product of the Day. Since then, we've been obsessed with one question: what would it take to actually trust an AI agent to run your receipt workflow the way you would?

• Added Fovea-1, a brand new model our best model yet. Way more accurate search results and better understanding of your files. Big leap in quality from the previous models.

• Added proper folder import you can now drag a folder from Finder onto the app, or use the new "Import folder" button in the add dropdown. It scans the entire folder tree recursively, finds all supported files, shows you a count, and imports them all at once. Brand new before this, you could only drop individual files.

• Fixed raw camera image decoding RAW formats (ARW, CR2, NEF, DNG, etc.) were coming out blurry or completely wrong because the Rust image library was decoding the tiny embedded JPEG preview instead of the full sensor data. Now it uses macOS's built-in sips tool for proper demosaicing, white balance, and gamma correction. Also generates a 1920px WebP preview that the detail view can actually display (browsers can't show raw files directly).

• Fixed the graph view so it actually makes sense the old cluster algorithm tried to tear the graph apart one connection at a time, which just didn't work for big collections. Replaced it with the Jaccard algorithm: it looks at how many shared neighbors two nodes have. If they share a lot of the same connections, they're probably in the same cluster. If they barely share any, they're a bridge between clusters. This finally gives clean, meaningful clusters instead of one giant blob.

• Graph threshold was lying the code logged one number for the edge cutoff but actually used a completely different one. Fixed so the displayed edges and the cluster detection actually agree with each other.

• Thumbnails aren't pixelated anymore on Mac macOS WebKit was treating a CSS flag as nearest-neighbor scaling, making every thumbnail look like a blocky mess. Swapped it for proper smooth scaling. Also bumped the internal thumbnail resolution so they're sharper even before the CSS fix.

• Search won't leave you with a blank page anymore if your search returns zero results, it now shows the 3 next-closest items with their similarity scores so you can click directly to them instead of staring at nothing.

• Search results were showing the wrong scores the merge algorithm was accidentally overwriting the actual similarity score with a meaningless rank-based number, so everything looked like it had the same ~3% similarity. Real scores are preserved now.

• Images load immediately when scrolling there was a race condition where newly visible cards in the grid wouldn't trigger their image load. Fixed so images appear the instant they enter the viewport.

• Graph stays crisp when you zoom the UI zooming the interface made the canvas go blurry because its internal resolution didn't scale with the zoom level. Now it renders at full resolution at any zoom setting.
  Feedback appreciated!

  

Nowadays the AI is dramatically improved product visual creation, but every workflow still seems to have one step that takes more time than expected. For me, maintaining consistency across a growing catalog and creating multiple variations still requires careful review.

I'm curious how others approach it:

• What's your current workflow that gives a better result?

• Do you still rely on manual refinements?

We're a small team. We can ship fast. We want to build what's actually useful.

So honest question what would make ExploreYC a tool you open every week?

Something strange happened last week while working on a side project we've been building alongside Murror.

I described what I wanted a feature to do not how, just what. The AI built it. I tested it. It worked. Not just "worked" it handled edge cases I hadn't even thought of.

Founder at @Decode by Entropik here. One of the things that surprises people most about MIRA is that we offer eye tracking: gaze, fixation, dwell time, heatmaps, attention of interest, using a standard consumer webcam. No Tobii. No IR sensors. No specialized hardware of any kind. 

The immediate question is always: how? 

Two ways my coding agent wastes my time.
One: I paste a screenshot and it edits the wrong element on a busy screen.
Two: it spins up sub-agents that wander off the task. Lately the wrong-element guess is the quieter, more frequent tax for me, but a few people swear the sub-agent drift is worse. Which one eats more of your day?