Connect with the Product Hunt community

You find an app that looks simpler or costs less. You try it, like it, then go back to the old one because moving your work feels like another project.

The awkward part might be:

I'm 19 and building Murmell with Gabriel.

Sometimes people are super supportive.

Add and maintain comparison tables inside an existing HTML page with HtmlDrag.

Insert a table, edit cells, manage rows and columns, apply a clear visual emphasis, and configure links. The guide uses an existing writing-course page and keeps the original descriptions available.

As a growth designer, I look at newsletters from two perspectives: how fast they prove their value, and whether they make me feel like I m giving away my inbox for nothing.

Getting an email address is relatively easy. The harder part is designing a sign-up experience that promises genuine value without feeling like a bait-and-switch.

Going through 40+ opt-in pages recently, a few things stood out to me:

Most pages use vague promises like "Join 10,000 readers." A high-performing page tells me exactly what I will learn in the first issue.
The best opt-ins don't ask for a commitment upfront they offer a free sample issue or an archive link so I can test the waters first.
Trust matters: the pages that kept me engaged showed a clear frequency (e.g., "One email every Tuesday") and a visible "unsubscribe anytime" button.

Hey Product Hunt! Michael here from ZeroClick.

We've added Jev-powered Seller Agents to our Agent Storefronts to help AI agents buy from your business faster, with fewer tokens spent figuring out how.

Some days I have a few agents open in parallel...

One on the backend.

Hi everyone,

Our last update here was 1.4.1. We're now at 1.22, and a lot has changed since the split panes, workspaces, and code graphs we first shared.

The focus has grown to coordinating the agents running inside those terminals: handing off work, seeing who needs a decision, and picking things up when you're away from your desk.

A few things worth catching up on:

Show me the version you have right now.

I d like to see what people here are working on before the demo is polished. A screenshot or a link is enough, along with what it does and the next thing you re trying to get working.

I m preparing to launch Inquir Compute, a platform for running apps, databases and background jobs. In my last post, I asked about tools people had built for themselves with AI. This time, I m interested in the projects that are still in progress.

What works already, and what s keeping you from sharing it with your first users?

Spent a lot of time analyzing competitors before launch, but once building started, all those notes became outdated pretty quick.

Tracking everything daily creates useless noise, but waiting months might mean missing major pricing or feature updates. Not sure what's actually worth keeping an eye on long term.

How often do you look at competing products, and what metrics or changes do you totally ignore?

The difference between a tool an agent chooses to call and a step that runs every time is the difference between a suggestion and a guarantee.

Microsoft's Copilot Studio documentation now describes a preview feature called hooks. The definition is plain: a hook runs one of your workflows automatically when something happens in your agent, and you use it "when you need something to happen every time, rather than only when the agent decides it's relevant."

Hi everyone,

This is a first look at the Autonomous Electronics engineer.

You give it a brief and it builds the board in stages: spec, block diagram, schematic, E-Sketch, layout, route, ECAD. Each stage is its own artifact you can open and inspect.

Our bold vision is for Everyone, regardless of their engineering know-how, to be able to create functional, manufacturable, multidisciplinary products using natural language - electronics, mechanical, controls and software/firmware. The same experience folks enjoy in tools like Lovable for vibe-coding, extended to complex, real-life systems.
We will continuously extend our part libraries for electronics and add specialized functions, like LED chip creation.
Soon we'll start a public PCB/chip library on our website, stay tuned.

Today we shipped JarvisCore v2.1.0 with fast RAG, stable atom life cycle, and better browser automation. Please refer to https://jarviscore.developers.pr... for more details (v.2.0.0 and v2.1.0). Test it out and let me know what breaks.
For more reads:

1. https://jarviscore.developers.pr...

2. https://jarviscore.developers.pr...

3. https://jarviscore.developers.pr...

Vibesmonitor now runs a daily site audit. It fetches each project the way a crawler does, with no JavaScript, and writes three reports. These are the issues that come up most:

Coding agents understand your repository well. They know very little about the machine it runs on.

Ask one to free up disk space and it often reaches for rm -rf. Ask what is using port 3000 and it pipes raw lsof output into the conversation.

Termi Protocol is live on Product Hunt again today. This one is built almost entirely from what you told us after the first launch.

The headline is the limit handoff. When an agent hits a usage, rate or context limit in the middle of a task, Termi saves the session (goal, changed files, commands, errors, open todos and the conversation) and hands it to an agent on another model, which continues from the last finished step. Nothing is sent until you confirm.

Also new since July:

Google started enforcing app registration in four countries three weeks ago, and the rollout widens in 2027. Most Play apps were registered automatically, but "most" is not the same as "yours".

Google's Android Developers Blog (18 June 2026) set 30 September 2026 as the date developer verification protections begin, starting with users in Brazil, Indonesia, Singapore and Thailand, on certified Android devices. Google's developer verification page says it expands globally in 2027 and beyond.

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?

I maintain Termexo. This AI-assisted update was checked against the 0.10.15 release notes.

This release is about finding the right project and making the next action clearer:

- Organize workspaces in nested folders, drag to reorder, and add tags and icons. Search the sidebar or open a project's directory from its menu.
- Choose Claude browser, Console or SSO sign-in, or Codex browser or device-code sign-in. The official CLI still handles authorization; its login terminal has a separate status.
- Discover models from a public directory and visible local Codex cache entries. Supported default profiles can show upgrade suggestions, which you review before applying. A catalog entry does not guarantee access through every account or gateway.
- Confirm before closing an active Agent terminal, so ending a process is an explicit choice.

Everyone has one. "Keep it short." "No emojis, ever." "My dog's name is Biscuit, stop calling him Buddy." The thing you've typed so many times you could say it in your sleep.

Here's the game:

1. Drop yours in the comments, exactly how you'd say it.

Building apps is my job, and AI is part of how I do it. After hours, I can't always tell if it's still work.

In Unprompt, I set my work hours once. It uses them to sort work from personal.

The blurry part is my own time: a side project at 10pm, a script for a friend on a Sunday.

How do you draw that line? Fixed hours, or a separate machine?

Hey all, a few updates since last time:

Genie, our AI Analyst, can already tell you what changed in your numbers. It's never been able to tell you why, because the why almost never lives in Databox.

Revenue drops 8%, and the real reason is a stalled deal in HubSpot, a pricing objection buried in a Slack thread, or a support ticket nobody flagged. Right now, finding that out means leaving your dashboard, opening three other tools, and piecing it together yourself. Every time.

Next week, we're launching MCP Connectors. Connect your CRM, Slack, support desk, or any MCP server, and your AI Analyst gets that same context, right inside the conversation. Ask why a number moved, and it points to the actual deal or thread behind it, not just the number.

Bring your own Anthropic, OpenAI, Google, or Mistral AI key for localization. Requests go directly to the provider on your key, and the provider bills you for those tokens.

Open Settings BYOK, add your provider key, and choose that provider s models in your localization engine.

Your key is used for the engine s translation and editing steps. Your integrations keep using its glossary, rules, and brand voice, while Lingo.dev runs the localization infrastructure.

DungeonQ is a defensive deception runtime for suspicious AI-agent sessions. A trusted gateway routes a designated session into a persistent synthetic world, with useful world-only Wrong Tickets, observable activity and separately approved bounded changes. The goal is to give people and authorized defender agents room to act.

v0.16 addresses a concrete lesson: protecting one route is not enough.

In the earlier Sol experiment, all three diverted sessions received the artificial target through an open alternate source, A2, despite zero reads through the main source route. Those failures remain published.

The repair applies shared tenant, resource and credential-version checks to the main source, alternate source, cache and export. A2 keeps no target copy. Cached content requires a fresh authority check; an unavailable origin produces UNKNOWN instead of stale disclosure. A world ticket or claimed role cannot grant source access.

Every Mac with Apple Silicon has a Neural Engine. More apps use it every month for dictation, transcription, and other AI that runs on the Mac.

Activity Monitor doesn't show it. I had no way to see how busy it was or which app was using it.