Connect with the Product Hunt community

Hi everyone, Matheus here, Toone's maker. We're preparing our next Product Hunt launch for September 18

Toone is a macOS app for crafting complex AI workflow automations and routines with natural language. I'd like to hear from people who want to try one small routine and share candid feedback.

If you're interested, share the task you repeat, the inputs you'd start with, and what a useful result would look like. Pick something you can check yourself so we can see where the routine helps and where it falls short.

I can help arrange access individually, though I can't promise immediate availability.
Thank you and see you by then PH

Bloated files are the worst part of maintaining a growing project.

We tend to hold onto old code because it feels like throwing away actual work, even when nobody has used that feature in months.

Cleaning up dead code always makes the app faster and cuts down build times, but it is super hard to convince the team to delete it.

Have you ever deleted a large chunk of code only to realize later that you actually needed a piece of it back?

Some time ago, I cleared off my entire desk getting rid of extra monitors, gadgets, and RGB lights and stuck to just a laptop on a bare table. No aesthetic plan, no productivity setup. Years later, I m still working this way, and my output has never been higher. Meanwhile, the elaborate productivity gear I spent hundreds on just created distraction. It taught me that removing friction beats adding fancy tools.
Have you ever simplified your workspace and found it actually improved your focus?

When you re hungry for feedback, it s tempting to listen to every user who has an opinion on what to build next. But recently, we realized that building for high volume free users was actually diluting the core experience for our ideal paying customers.

Saying no to enthusiastic users is tough, especially when you want to keep your community active and engaged.

For founders who have balanced early feedback loops: how do you systematically separate high-value signal from broad feature request noise?

We re giving agents access to APIs, databases, CRMs, payments and internal systems.

But something feels missing.

We can observe what an agent did.
We can evaluate whether it was right.
We can detect a policy violation.

I've started asking one thing before I give anyone advice about their product. Do you want me to help you think, or do you want me to tell you what I would do?

They are completely different conversations and most of the time people want one and receive the other.

When I'm trying a new SaaS tool, I'm much more interested in signing up if I've already seen what it can actually do. Being asked to fill out a form before seeing any real value can make me leave before giving the product a chance.

I get why founders ask people to sign up upfront, though. It helps them save their work, personalize the experience, and understand who's using the product. And some tools need a bit of setup before they can show useful results.

Personally, I like the idea of letting someone try one small part of the product first, then asking them to create an account when they want to save their work or go further. But I'm not sure that approach makes sense for every type of SaaS.

AI is great at producing a first landing-page draft. The last mile is still human: make the promise specific, make the CTA match the next action, remove repeated filler, add a link or table only when it helps a visitor decide, preview the whole page, and export the reviewed HTML.

HtmlDrag gives teams a visual working copy for that focused pass. Keep the HTML that already works instead of restarting the page because one visible decision needs correction.

This release is about doing more with fewer clicks, and making the app yours. A good part of it came straight from your reports and requests, so thank you for that.

Here is what's new.

Connect to Server, redesigned

MinkNote is a privacy-focused Mac app that keeps everything you write and collect in one place, organised and effortless to find again.

Until this week it ran on a 14-day trial, then all the notes went read-only. Two weeks is not long enough to know whether an app like this fits your workflow, so now it works the way most Mac apps you already use do:

Someone bought my product a year and a half ago. Paid once. Never upgraded. Never asked for anything.

Then they emailed me out of nowhere with a detailed explanation of a problem they'd solved with it. Something I'd never thought it could do. They'd built a whole process around it and wanted to tell me.

Existing workbench screenshot (v0.8.0), shown for context.

I'm the maintainer of Termexo, an MIT-licensed Windows workspace for Claude Code, Codex and OpenCode.

v0.8.7 focuses on a frustrating reliability problem: an agent could keep running while its terminal went blank and appeared stopped. Resizing around a wide character could trigger a parser panic, poison the screen mutex and leave subsequent screen reads failing. Switching between clients could reproduce that combination.

When a problem needs a diagram to explain, I don't do it all through a blind call we just look at the same thing and work on it together.

"LiveSyncDesk is Not an another Online Whiteboard, It's the moment inside a conversation when words aren't enough.

LiveSyncDesk is a small real-time visual explanation space during a conversation."

Move through your inbox with the arrow keys, enjoy clearer summaries, and give your Mac more breathing room.

Fly through your inbox

Use the arrow keys to move through emails and groups in the order you see them. Your selection stays clear of sticky controls, and focus follows along after archiving or undoing.

I added logging. The log line didn't appear. I assumed the code wasn't executing. I restructured the function, added more logs, restructured again.

Four hours later I found it. The log line was there. It was being written to a file I wasn't tailing because the path had changed two deploys ago and I was looking at the old one.

I used to answer every message within an hour. Email, support, DMs, comments. I wore it like a badge.

Then I let some things sit. Not everything. Just the ones that weren't urgent, weren't from customers, weren't actually about the work.

Introducing Aura by Neural, our state-of-the-art personal AI.
Launching on macOS in just a couple of days.
AI shouldn t be somewhere you go.
With Aura, intelligence is simply there, available anywhere on your computer, already understanding what you re working on, remembering you, and ready to talk or act.
Aura gives you access to the cutting edge of frontier intelligence together with NeuralAction, our flagship computer-use model.
But the technology isn t the point.
What changes for you is.
You stop opening AI apps, copying context, explaining what s already on your screen, and manually doing every little step yourself.
You start spending more time deciding what you want done.
Call Aura.
Say what you want.
Keep moving.
Over time, Aura becomes personal to the way you work and live.
Built for people who want more leverage, less friction, and access to the frontier without constantly chasing it.
Intelligence is no longer an app. It s the computer.
Check it out:
https://aura.withneural.com

I've noticed that some UI terms are easy to mix up, especially when working across different platforms.

For example, iOS uses "Navigation Bar" for the top area with a title and actions, while Material Design calls a similar component a "Top App Bar."

And on Android, "Navigation Bar" can refer to the system navigation area at the bottom of the screen.

These aren't just different names for the exact same component. Each platform has its own terminology, guidelines, and interaction patterns.

someone on my last thread pointed out the project file says what the project is, but not what changed since yesterday. i don t have a good answer for that yet.
what do you do, just let it read the git log?

I asked Claude Code to rename a function across the codebase. It found 12 files, made the change, and reported success.

A thirteenth file sat in a directory outside its search scope. No warning.

Termexo v0.8.6 AI-generated release illustration

I maintain Termexo, an MIT-licensed Windows workbench for Claude Code, Codex and OpenCode. Version 0.8.6 focuses on reloading a view, reconnecting remotely, resizing a window and switching to a terminal that was hidden.

Keep the running process
Previously, frontend loading could be mistaken for a new terminal launch. Reloading could restart an agent that was already working. The view now reconnects to a backend terminal that is still alive, preserving its current launch and avoiding redundant session takeover requests. Closing Termexo or shutting down the computer still ends running processes.

After a few months of beta testing and gathering feedback, we've started implementing some changes, and we're excited to share them here!
Branda v1.1 is Live
More controls and better experience.
50% Faster
Model selector (GPT images 2.5 + Nano for now)
Quantity selector (low + medium)
Visual prompt UX (better ux)
More prompt ideas to expand your brand (look at prompt suggestions)
Much more details

Check it out here www.branda.co

With the amount of automation I have built, the number of websites deployed, and a clear understanding of environment variables (learnt that the hard way), I wanna give building a product a try. Obviously, it is not an easy task, and I am no expert. But I am looking for ideas. Something that you would want to exist. Something a novice I can try building by myself (with your help :)
So... where should I start with?

Perhaps local setup, CI, containers, and AI agents all follow slightly different paths, and a green result does not always mean the same thing.

Ota is offering a free execution-readiness review for a small number of open-source projects and engineering teams.

We ll review one selected repository, identify conflicting or incomplete execution paths, and prepare a reviewable draft integration showing:

• the canonical setup and verification path;

• which native, container, and CI lanes actually work;

• what each result proves;

• what remains unverified.

A monthly active user metric can look completely stable while underlying product usage slowly drifts into a passive state.

Realizing that logins do not equal active value creation made us completely rethink how we track long term retention.

For founders looking past the initial growth phase: what retention metrics actually give you an honest signal about product health?