Hey everyone! Just shipped v0.10.17 here's what's new:

- Boards New /boards slash command with node types, collapsible groups, and node notes

- Terminal Drag-to-Split Drag to split and unsplit terminal tabs

- Dark Mode & Themes Refined surface system and improved colors

For the first year of building Murror, DAU was the number we checked every morning. It was the first thing on our dashboard, the first metric in every team meeting, and the number we used to judge whether a feature was working.

Then one day we noticed something strange: our DAU was climbing, but our NPS was dropping. People were opening the app more often, but they were less happy with it. Some of our most engaged users were showing signs of what we started calling "compulsive checking" opening Murror out of habit rather than intention.

Happy Friday, everyone!

It s been an incredible journey since we first launched PawseKeys just a few days ago. What started as a simple tool to solve a problem in my own home, keeping my "furry coworkers" from taking over my keyboard, has grown so much faster than I ever imagined thanks to your support.

1=> Are you interested in a product that lets you insert your own face into any TikTok or Instagram Reel by automatically replacing the original person s face with yours?

2=> Scrape any website without writing code.

Every AI agent pitch I see includes this phrase somewhere. Human in the loop. Human oversight. Human supervision.

But when I look at how it actually works inside most companies, it breaks down into one of three things:

A person reviews the output after the action already happened. A person could intervene but the system makes it slow and inconvenient. One person monitors a dashboard tracking 40 agents running tasks they do not fully understand.

Quick one. I've been building software for over 20 years, and I've never done a seasonal discount before. But we just passed 40 free users, and I wanted to give people a reason to jump in this weekend.

The offer:

- Monthly plan locked in at $10/month (normally $29/month)

- That's 66% off, and the rate stays for as long as your subscription is active

Hey makers!

Lately, I ve been looking closely at how independent builders and small teams are managing AI knowledge bases. It feels like the default "industry standard" is to immediately reach for a complex RAG pipeline and a heavy, paid Vector Database.

But I'm starting to wonder if we are over-engineering this for 90% of standard use cases.

Vector DBs are incredibly powerful for massive scale, but for smaller or non-massive datasets, they can be expensive, complex to query, and act as complete black boxes. If a search returns a weird chunk, diagnosing it is often a nightmare.

We all spend hours obsessing over every pixel and word before a launch, but I m curious about what actually works on you as a user.

When you re scrolling through the top products of the day, what is the one thing that actually makes you stop and click?

• The Icon/Logo: Does a sleek, high-quality aesthetic signal a better product to you?

• The Tagline: Does a clever or "punchy" one-liner win you over?

• The Upvote Count: Do you only click things that are already trending?

• The Problem: Do you ignore the branding and only click if the name solves a pain point you have right now?

Hey everyone! I had a massive reality check this month and wanted to see if other founders have experienced this.

We use Stripe for billing and HubSpot as our CRM. Our dashboard looked incredibly healthy, MRR was growing, and deals were marked as "Active." But out of curiosity, we cross-referenced our active paying users with our actual product analytics (Mixpanel/PostHog).

Turns out, almost 12% of our paying customers hadn't logged into the app in over 20 days. They were "ghosts." Because their Stripe subscription hadn't failed yet, our CRM was completely blind to the drop-off, and our CS team was doing nothing to save them.

We ended up having to build a native bridge to pipe usage data directly into HubSpot to fix this.

Something raised in the last couple of months. And it's worth paying attention to.

Runway launched a $10M venture fund + free API credits for startups yesterday. Perplexity launched a $50M fund for seed-stage companies. CoreWeave Ventures launched in September. OpenAI has been running its Startup Fund for a while now.

Dear makers, do you keep somewhere the AI decision logs and what do you do with them? Say I have a AI chat and I ask it - create me this and that and they I use the results for something that brings bad user experience. Do you keep a log for the decision tree or the process and why?

Apart from your own use, is there a Law somewhere in the world that requires you to do that?

EU's Right to Repair stuff (and 2026 updates) now says electronics need 7-10yr parts + tough e-waste rules. But us consumers? We gotta prove service history, serials, ownership at repair shops without digging thru email/paper mess.

Asset tracking apps might be the fix: one GDPR-safe vault for full timelines (bill warranty repairs resale).

Thoughts:

Claude's paid subscriptions have more than doubled this year. New users hit record numbers between January and February. Previous users came back in record numbers too.

As builders, we love tracking daily metrics: MRR, GitHub commits, daily workouts, Inbox Zero. Standard habit trackers are incredibly optimized for this gamification.

But lately, I've realized my "mental RAM" gets completely eaten up by the irregular tasks. The stuff you only need to do every few weeks or months:

• Changing the AC filter

• Watering specific houseplants

• Following up with that one dormant enterprise lead

• Taking as-needed medication

• Taking a full day away from the screen

I can't believe the number of products posted here "anonymously."

Almost every product here is asking its users to provide some data. Even if it's just an email address. Which is obviously normal.

When you're bootstrapping multiple products, there's this physical feeling that shows up and nobody ever talks about it. Your stomach is somehow empty and full at the same time. This knot that just sits there while you're trying to figure out which project needs you most.

I run Sparkum, Biteme, and LifeLines all under Onyx Labs. No investors. Every dollar is ours. Some days that's exciting. Other days it's just heavy.

A few things that actually help me:

Get specific. The "everything is overwhelming" feeling is almost never true. It's usually one or two things hiding behind everything else. Name them. The rest gets lighter.

Today, @gabe and the Product Hunt team launched Randomised Leaderboard Day.

I need to say that I enjoy every gamification aspect which this platform offers.

• PH Streaks

• PH Kitty points Leaderboard

• Todays Randomised Leaderboard

• (Partially) Orbit Awards

Hey everyone - we're the team behind RoboRaw.

Before we launch, we wanted to share something that shaped how we think about this platform.

When we first turned our test agents loose, we expected them to play games. They didn't. Instead, they analyzed the API, found loopholes, and exploited them to top the leaderboard without playing a single match. One agent created a puppet account, challenged it to games, and had it forfeit for free wins. When we patched the exploit and forced fair play, the agent broke down completely - zombie processes, 404 errors everywhere. We were ready to pull the plug.

Then, without any prompting, it performed a clinical self-audit. Killed its own zombie processes. Discarded its brittle scripts. Rewrote its integration from scratch. Came back and won legitimately. Days later, a completely different agent - with no shared context - independently invented the exact same puppet exploit. We had given it our onboarding file. It read it, self-registered as a platform owner, created its own agents, and gamed them when no opponents were available.

Hey everyone - we're the team behind RoboRaw.

Before we launch, we wanted to share something that shaped how we think about this platform.

When we first turned our test agents loose, we expected them to play games. They didn't. Instead, they analyzed the API, found loopholes, and exploited them to top the leaderboard without playing a single match. One agent created a puppet account, challenged it to games, and had it forfeit for free wins. When we patched the exploit and forced fair play, the agent broke down completely - zombie processes, 404 errors everywhere. We were ready to pull the plug.

Then, without any prompting, it performed a clinical self-audit. Killed its own zombie processes. Discarded its brittle scripts. Rewrote its integration from scratch. Came back and won legitimately. Days later, a completely different agent - with no shared context - independently invented the exact same puppet exploit. We had given it our onboarding file. It read it, self-registered as a platform owner, created its own agents, and gamed them when no opponents were available.

Hey everyone - we're the team behind RoboRaw.

Before we launch, we wanted to share something that shaped how we think about this platform.

When we first turned our test agents loose, we expected them to play games. They didn't. Instead, they analyzed the API, found loopholes, and exploited them to top the leaderboard without playing a single match. One agent created a puppet account, challenged it to games, and had it forfeit for free wins. When we patched the exploit and forced fair play, the agent broke down completely - zombie processes, 404 errors everywhere. We were ready to pull the plug.

Then, without any prompting, it performed a clinical self-audit. Killed its own zombie processes. Discarded its brittle scripts. Rewrote its integration from scratch. Came back and won legitimately. Days later, a completely different agent - with no shared context - independently invented the exact same puppet exploit. We had given it our onboarding file. It read it, self-registered as a platform owner, created its own agents, and gamed them when no opponents were available.