Connect with the Product Hunt community

I cofounded Zeplik, every frontier model in one chat, switchable mid conversation without losing context. Now building Arteza on the same idea for image, video, voice and music.

Most of what I've learned this year isn't the fun part. It's context handoff between providers who all format history slightly differently. It's pricing something whose underlying cost moves every few weeks. It's support tickets from people who don't believe the model actually switched, because the tone didn't change enough for them to notice.

Six months ago we added an AI feature to Murror that we were sure would be a breakthrough. It analyzed journal patterns and surfaced emotional insights -- things like "you tend to feel more anxious on Sundays" or "your mood improves when you write about specific people."

The insight quality was genuinely good. We tested it internally, everyone was impressed.

Swap USDC USDT / USDT USDC or convert into any SOL token in seconds. 0.33% fee, no hidden spreads.
Connect your wallet and try it now: https://sendr.cash/swap
#SolanaCommunity #solana #swap #sendr

https://github.com/hetima/sigma-...
It should already be available in the app

Launching an app is one thing. Getting those first users is a completely different challenge.

Instead of spending money on ads, I d rather give the app to people who are willing to try it and share their honest feedback.

I m giving away 100 lifetime licenses for PanicMode.

Just use the coupon code PRODUCTHUNT at checkout to get a 100% discount.

Hey everyone !

Just shipped a big update to IdleDev and wanted to share it here first.

Quick recap if you haven't seen it: IdleDev fills the dead time in your AI coding sessions. While Claude, Codex, Gemini (etc.) are thinking or running tools, a clean sponsor sidebar runs right beside your agent in the terminal. Developers get paid for that idle screen time, advertisers get a direct line to devs. No tracking pixels, no popups.

What changed in v2:

Hey everyone!

Just wanted to share a brand new tool I've been working on that's launching today on Product Hunt,

hey folks, today I ran a couple of agents to take more data and push them to the platform - had the idea to use ProductHunt.. and so we did it!

we are at over 8.5k companies now!

I realized most of us breathe all day without ever thinking about it.
Do any of you intentionally practice breathing whether during workouts, meditation, yoga, before sleep, or just to calm down after a stressful day?
Has it made any noticeable difference for you?

AI agents can now run reliably for hours, days, and even across system failures.

But keeping an agent running is only half the challenge. How do you ensure every action it takes is authorized, controlled, and auditable?

That is why @OpenBox is partnering with @Temporal .

The integration brings runtime governance directly into long-running Temporal workflows. Builders can:

I used to plan my lunch breaks around AI tasks. Pick the one task that's easy enough to just hand off, start it, go eat.

Came back more than once to find the agent had stopped two minutes in over some dumb question. Not even a permissions thing, it just sat there waiting for me to say "go ahead". Didn't even know it was stuck until I checked.

Since launching on ProductHunt we've been doing a lot of thinking. Conversations with fleet managers, feedback from this community, and honest reflection on what detectly actually is versus how we were describing it.

We got the framing wrong.

detectly isn't another fleet safety tool. It's the layer that sits between dashcam footage and action. The dashcams are already there. The footage already exists. The gap was never hardware, it was the missing layer between footage and insight.

That's what we're building. The AI safety layer for fleets.

Quick heads-up before tomorrow.

Linear is now where teams keep their whole product context - issues, project decisions, cycle history, planning docs. That's a lot to have in one place, and worth protecting.

Excited to launch the Parsewise MCP
You can now connect Parsewise directly into tools like Claude, Cursor, and other LLM tools.
That means you can ask questions across your documents, extract structured data, and pull answers with citations, without leaving your workflow.
Here is a video on YouTube with an example of how it's used: Parsewise MCP Demo

I have spent this week arguing here that the real problem with AI tooling is memory that does not survive a session. Then I looked at my terminal and realised the argument had been sitting in front of me the whole time. Shell history is the memory system every developer already owns. It has been running for decades. By default it is worse than anything we would ship today. A flat file. No context. Truncated at some arbitrary line count. Gone when you switch machines. It records what you typed and throws away everything that made it meaningful: which directory you were in, whether it worked, how long it took. We would never accept this from a new product. A notes app that stored notes without dates, silently dropped the oldest ones, and did not sync would get laughed off this site. Shell history gets a pass purely because it has always been that way, so nobody counts it as a memory system at all. It is just there, quietly useless. What changes when you fix it is not storage, it is the question you can ask. "What did I run in this repo that actually worked" is a different question from grepping a text file, and it is the question you actually have. Exit codes turn a log into a filter. Directory context turns global noise into per project memory. Duration tells you what was expensive. So the claim: most memory problems are not storage problems, they are context at write time problems. The data was there. Nobody kept the fields that would have made it findable later. What is the one field your history does not keep that you would actually use?

we are taking the 1st place upon launch! let's goo

OpenAI just made AI memory automatic.
The problem? you can no longer fully audit what it remembers about you.

Dreaming V3 (launched June 4) doesn't ask you to save memories anymore. It runs in the background, reads across years of your conversations, and synthesizes a profile of you, and automatically updating as your life changes.
It remembered your Singapore trip was in the future. Now it knows you went. You didn't tell it that. It figured it out.

The audit trail problem: TechTimes reported the update "limits" what users can actually see. You used to have a list of saved memories you could read and delete. Now you have a synthesized profile that's broader than that list, and you can only partially inspect it.
A CHI 2026 study called it the "personalization-convenience paradox": the feature users value most is also the one they can least control.

We just put Buddy on iOS and Android today, and the thing I didn't expect: I capture totally differently on my phone. At my desk I type. Walking to lunch or lying in bed at 11pm, I just talk. Half my best notes now start as me mumbling into my phone.

But I know dictation is divisive. Some people live in voice notes, others would rather do anything than talk to their phone in public

Pasting a screenshot into a terminal agent is messier than it should be. On macOS Codex wants Ctrl+V, not Cmd+V. Claude Code on Windows wants Alt+V. Some terminals just eat the image. So people end up saving the shot to disk and referencing the path by hand, which kills the flow.

What's your real workflow, drag and drop, the --image flag, save-and-reference, something better? Trying to map how people actually do this.

Last quarter, our team spent three weeks building a feature that does... nothing.

When a user writes something deeply painful in their journal grief, heartbreak, feeling lost Murror's AI used to respond immediately. Empathetic words, gentle reflections, suggested reframes. Users loved it in surveys. Our response quality scores were excellent.

BREAKING: @Dimension is acqui-hired by @Granola.

@Dimension was a proactive AI assistant for engineering teams that removes context-switching. First launched on Product Hunt last year, the product ranked Top Product of the Day, and Developer Tool of the Week.

You spend 4 hours on Cursor or v0. You prompt, the AI generates, and your app comes to life right before your eyes. It s smooth, it s thrilling. An instant hit of dopamine. You feel like a tech genius.

Then comes the time to market it.

Suddenly, you have to open Meta Ads Manager, write hooks, script a video, fight the algorithm, and potentially face total market indifference. All that high energy immediately tanks. It s slow, it s thankless, and it s uncomfortable.

The brutal truth: Vibe Coding has made building so easy and addictive that we unconsciously use it as an excuse to procrastinate on distribution. We d rather stack a 12th feature in our safe space than go out and hunt for our first paying customer.

we asked ChatGPT, Perplexity, Claude, and Gemini 41,400 real customer

questions like "best hotels in New York" and "top HVAC in Phoenix" across

690 US markets. Then I asked the exact same questions 7 days later.

391 of 690 markets had a completely different #1 answer.

Look, We all know that "premium email apps" have been around for a long, long time.

But why is it still such an untapped topic that nobody seems to talk about?

And why does gmail still hold 80% of market share?

We all have that one repetitive thing. Takes 15 30 minutes. Feels like it could be automated. But you just keep doing it by hand.
Every Friday, I manually copy data from three different dashboards into a Google Sheet, reformat the dates, and email it to my team. Takes 25 minutes. I've told myself "I'll automate this" for six months. Still doing it by hand.

What's yours?