Connect with the Product Hunt community

Two honesty fixes this round: octoscope now tells you when a newer version is out, and it counts your whole account instead of just the first 100 repositories.

The update notice

On launch and hourly after that, on its own timer separate from the dashboard refresh octoscope checks the public Releases API and, if there's something newer, drops a quiet one-line notice under the banner. The upgrade command is context-aware: it detects how you installed octoscope and suggests the right one brew upgrade, go install, gh extension upgrade, or a download link.

Netfox 0.5.0 just shipped, and it's the release that makes the menu bar the place to watch your network plus the port scanner finally checks the ports you care about.

Live traffic, one click away. The menu bar popover now charts your Mac's download and upload over the last minute a filled curve for down, a line for up, live readouts next to them. It samples for the whole life of the app, so the chart opens already full of history. No setup, no special permissions.

We re teaming up with @Vercel for a special launch day on Product Hunt.

If you re building on Vercel, schedule your launch for midnight PT on April 17 and tag it under 'Vercel Day' to be included in a dedicated leaderboard for the day.

From Jeff Wang, Prev. Windsurf CEO now President, New Enterprise at Cognition/Devin (who just raised $1B):

Today we are saying goodbye to Windsurf

and we are transforming it to Devin Desktop

Windsurf has been an absolutely amazing experience for me and the team. Though it has been rocky at times, we have seen every phase of AI coding and we want to keep embracing where things are going. That means we need to once again reorient ourselves towards a more focused goal and remove the Windsurf branding.

Believe it or not, the Windsurf brand has been around less than a year and a half, and before that, the previous name Codeium was only around a similar timeframe as well. I ve actually had to change my email every year all the way to the eventual acquisition to Cognition. In AI, most products only have a 1 year lifespan before you need to drastically change it to the next.

Devin now encompasses all our form factors, whether it s the cloud agent, the agent command center (with IDE), CLI, review, or our other products. This way we can really focus our efforts around one name. We are doubling down on our neutrality and making Devin Desktop compatible with other agents via ACP. We may be the only Switzerland of AI left and we embrace this role.

As for me, I ll be transitioning from CEO of Windsurf to Cognition s President of New Enterprise, helping open new regions and verticals, accelerating velocity, and filling in gaps as usual.

The story of Windsurf doesn t end here, it continues on as part of Devin s journey.

I still rock Windsurf and love it, despite all the handwringing about pricing.

Over the last decade, countless people have launched products here every single day, so there's certainly no shortage of inspiration.

And I have to say, the bar keeps getting higher (helped in part by the fact that some launches are filtered through the Featured section).

Two releases since split panes landed. Here's what shipped.

v0.27 Pins & Notes

You know the "found this, not ready to fix it yet" pile? Now you can pin any terminal output to a per-project rail and work it as a checklist. Title + body per pin, drag to reorder, done items collapse. Works inside full-screen TUIs like Claude Code, not just plain shells. A notes scratchpad sits under it and autosaves per project.

Hey PH, we've been blown away by the response to our launch :) thought to share a quick update on what's happened since:
User success:
-we had a huge user spike: 250+ new companies are using Causo for fundraising since our PH launch
-we're seeing that many people join early, look around the investors database, then convert once they're ready to actively raise
-we saw users send out 400+ investor emails and get 26 replies; avg reply rate of 6.5%

New stuff:
-Ivan and I have drank SO much coffee, deepened our eyebag colour significantly, and shipped a bunch of stuff:
-one-click connect for Microsoft inboxes
-50+ new free resources for sales and GTM over at https://hub.causo.ai/
-bunch of UI fixes - thanks so much for everyone who had feedback, it was all so helpful!
-we're rolling out Causo for Sales in early access: tell Causo who you need to reach, Causo finds people and writes to them. Similar no nonsense AI raccoon stack, but now for b2b sales instead of VCs.
If that sounds interesting (who doesn't need more leads) drop us a shout, we're onboarding first companies selectively :)
Back soon with another raccoon update!

Most software wants you to come back every day. The business model depends on it. More sessions, more engagement, more opportunities to monetize.

But what happens when your product's purpose is to help someone understand themselves better? At Murror, we've been wrestling with a paradox: if we do our job well, users should eventually need us less not more.

I'll start.

Supabase. Found it here three years ago. Thought it was just another backend. Now I can't imagine building without it.

Here's what it does for us at Rankfender:

Auth that doesn't make you crazy. We have users across 120+ countries. Supabase handles sign-ups, logins, password resets, magic links, OAuth with Google and GitHub. It just works. We didn't have to build any of it.

A few days ago, we launched mailX by mailwarm (YC S20) on Product Hunt. We finished #2 Product of the Day.

And today, we re launching @Mailwarm2.0.

The obvious value of Product Hunt is visibility: traffic, followers, backlinks, social proof, maybe customers.

But honestly, the part I m starting to value even more is the GTM learning.

Something that keeps coming up when I talk to teams about AI code governance: everyone focuses on capturing records, but almost nobody asks how confident they are in those records.

There are two very different things you can have.
Record A: a file-watcher noticed 47 lines appeared in auth.py and Cursor was probably running.
Record B:a proxy intercepted the Anthropic API call, matched it to the editor insertion via request UUID, measured 1.4 seconds between the API response and thecode appearing, and computed 0.81 trigram similarity between the model output and what landed in the file.

Both produce a row in your audit database. The second is dramatically more defensible but most governance tooling treats them identically.

In LineageLens, every record gets a confidence score from 0.0 to 1.0, broken into five independent evidence signals. Easy Mode captures (VS Code extension, no proxy) score around 0.27 honest about what you know. Power Mode captures (proxy running, full request interception) score up to 1.0. The score is not about whether the record is useful. It is about how much you can defend it when someone asks.

SQL definitions: reusable snippets across your queries

You can now create SQL definitions scoped to a database connection versioned, named SQL snippets that you can reference inline in any query with {{ definition("name") }}. Definitions get their own home in the Data page sidebar where you can create, edit, describe, and preview them, and the expansion is applied both for human-run queries and for queries the chat agent runs on your behalf.

The chat agent understands definitions too, so when it writes SQL it can reach for your team s definitions automatically. Admins can also let the agent propose and save new definitions when it spots a pattern worth keeping around so the SQL your team relies on becomes a real, reusable building block instead of something everyone re-types.

I've noticed more people using second-brain in ways I didn't expect when I created it, and I want to record that somewhere.

This thread is for sharing how you actually use the REST API or CLI in your daily routines. I m not looking for the obvious tips from the README, but rather the workflows you've created, the scripts you're running, and the things that turned out to be more helpful than you thought.

A lot of large companies (not just tech giants) are laying off employees at scale because AI can already do parts of their work faster, in higher volume, and at a comparable level of quality, sometimes even better.

At the same time, companies are starting to openly admit something important: AI is expensive.

Many of us use it for text generation, image generation, and making tasks fast.

That is something repetitive, and over one week or so, it is not so mindblowing anymore.

If I could sum up building in public in two words, it would be: course correction.

We launched AI Context Flow on Appsumo a few weeks ago, and turns out, managing AI context across tools is more nuanced than we thought. Thousands of people tried our product and one piece of feedback kept recurring: users needed more control over memory curation.

The demand was clear, but our product had missing features. So we did what any startup team does: we course corrected and went to our cave to build out what users needed.

Here's what we just shipped:

We launched Shadow lat week and the response blew us away. Thank you to everyone who upvoted, commented, and shared. #2 Product of the Day means a lot to a small team building in public.

For those just discovering us: Shadow sits on your calls and gets the post-call work done while you're still talking. No extra time, no context switching, you hang up and the work is already in progress.

For the first year of building Murror, we optimized for the same metrics every other app optimizes for: daily active users, session length, screens per visit. The dashboard looked healthy. Usage was growing. We felt good about it.

But something was off. Our most engaged users were not our happiest users. People who spent the most time in the app were often the ones who left the harshest feedback. Meanwhile, users who opened the app twice a week for five minutes were writing us emails about how it changed how they handle difficult conversations.

Three months ago, we added the most terrifying feature in Murror's history: a single button that lets users permanently delete every insight, pattern, and memory their AI companion has built about them. Months of emotional context, journaling patterns, relationship dynamics -- gone in one tap.

Our investors thought we were insane. Our product team debated it for weeks. The data team warned us we'd lose our most valuable asset: the personalization layer that makes Murror's reflections feel meaningful over time.

I will go first.

The meeting where everyone nods and no one disagrees.

Not because they agree. Because they have checked out. They do not think their opinion matters. They have stopped investing.

That silence is louder than any argument.

I remember there was a time when the Product Hunt team had a subcategory called AMA, which felt a bit more exclusive.

A special guest would show up with a post like I m X, founder of X, AMA, and those sessions were actually quite successful in my eyes.

People s motivations for wanting something of their own vary quite a lot.

So far, though, I ve most often heard these three answers:

• To make a lot of money.

• To work really hard until 30 so I can relax later in life.

• Time and location freedom.

Lately, after spending a lot of time online, I ve noticed that the way I consume content has changed, and honestly, not for the better.

When I consume content on social media (or through screens in general), I tend to pay less attention, and my attention span feels much shorter.

Vokal got #2 product of the day and #7 of the week, and we now have 100+ signups from startups and teams. In general, people seem excited to try it out to up-level their teams to agent native.

Now I m trying to figure out the next step: how do we scale this beyond manual founder-led work?

I ve been writing posts, sharing content, and doing outreach manually, but it s starting to feel like a constant drain and a bottleneck. I ve been looking into tools like HubSpot, LinkedIn Sales Navigator, Apollo, and Clay.

For people who have used any of these: what has your experience been? Which ones are actually worth it at an early stage?

Terminal or editor-first UI? How do you prefer to work with AI coding agents?