After months of building this thing, the first-ever StreakWars game is finally starting.

The rules are borderline stupid:
📸 Everyone joins the same War
⏰ You have to post proof before the clock runs out
💀 Miss once = you’re fucking out
🏆 Last person still alive wins the pot

That’s it.

No XP. No levels. No 45-minute gaming sessions.
We built it because we’re adults with jobs, meetings, kids and approximately 11 minutes of free time…
…but somehow we’ll still spend 45 minutes talking shit in a group chat.

So we thought:

What if the group chat WAS the game?
Something you check for 30 seconds a day, talk an unreasonable amount of shit about, and slowly watch your friends get eliminated because Kevin forgot to take a fucking selfie on Tuesday.
And now we’re actually testing it.

WAR #001 starts soon.

Which is mildly terrifying because this will be the first real StreakWars game ever played.

The rules will probably evolve.
Something will probably break.
Someone is absolutely going to get eliminated in an embarrassingly stupid way.

And one psychopath is going to outlast everybody.

So before we start, Reddit gets to decide something:
What would YOU be most likely to survive?
A) Daily selfie
B) Outfit check
C) Photo of your lunch
D) Couples selfie
E) Something considerably more unhinged — comment it 👇

Also:
How many days do you genuinely think you’d last?
I’m saying 6 before half of Reddit forgets. 😂
If you find StreakWars right now, you’re ridiculously early.

No giant community. No polished corporate launch.
Just War #001 and a bunch of strangers about to find out who has their shit together.

May the least forgetful idiot win. 🫡

Hi all,

As i'm working on growing launchpact.io i'm seeing a lot of unprepped launches and as the day unfold they don't get much visibility and end up with a failed launch.

This is one of the reasons i build launchpact.io, if you have an upcoming launch do check it out and prep ahead of time, i also added this checklist that can give some hints too, have a read.

Good luck everyone!

Solo dev here. I kept owning things and forgetting where I put them, so I built Store & Forget.

The whole point is zero effort to catalog: you don't type or tag anything. Snap a photo and it auto-fills what the item is (the photo scan uses a cloud AI service). Later you find it by searching names, descriptions, or which box or room it's in, or tap "Smart Find" to search by meaning.

Local-first: everything sits in an on-device database, no account, no sign-up. Optional backup to your own Google Drive.

It's free, Android only. Would love feedback from other builders.

https://play.google.com/store/apps/details?id=dev.koalalab.storeandforget

I built HeyZoku.
PH - https://www.producthunt.com/products/heyzoku/launches/heyzoku-hands-free-coding

As the models are getting much better at understanding us directly via voice, we should be working towards finding more ways to improve our productivity and do better work. And shouldn't be limited to just chat/keyboards to do our work. With how humans naturally communicate with each other, it should be the same way with the machines, a human shouldn't need to learn how a computer works - it should be natural.

So today I am launching HeyZoku - Hands Free Coding. So you can control all your coding agents just with your voice and complete your work without any need to continuously touch your keyboard.
I am using Nvidia Parakeet to make it work completely offline - so it can work completely offline. (It also has an optional bring your own openai-realtime key for more natural and multi language support.)

Open to any kind of questions or feedback and thank you for your support.
An upvote would mean a lot!

I kept doing this thing where I'd find something I wanted to deal with later — an article, a product restock, a ticket sale, a deadline, some documentation, whatever — and I'd leave the tab open.

Then 3 days later I'd have 30 tabs open and no idea why half of them were there.

Bookmarks didn't really solve it either, because they remember where something is, but not when I need to come back to it. And setting a reminder on my phone meant getting an alert on the wrong device and then having to find the page again.

So I built Latr.

The idea is pretty simple:

Find something → remind yourself about it → forget about it → Latr brings the exact page back when you need it.

For example, if I'm looking at a page about a ticket sale starting Friday at 10 AM, I can highlight the date, right-click and tell Latr to remind me about it. It saves the page along with the reminder.

When the time comes, I get a notification and clicking it takes me straight back to that exact page.

There's also a keyboard shortcut (Alt + Shift + Y) if I just want to save the current page quickly.

I built a bunch of other things around the same idea too — recurring reminders, snoozing, notes, folders/tags, calendar handoff, importing existing links, etc.

One thing I was particularly intentional about is privacy: there's no account, no backend, no analytics, and no telemetry. The reminders stay in the browser.

It's completely free right now.

🔗 Chrome: https://chromewebstore.google.com/detail/latr-%E2%80%94-remind-me-about-th/lcceeepfhggkninbfbifkpalkdoinjli

🌐 Website: https://latr.page/

I'm sharing a short video showing how it works too.

This is my first time putting something I've built out there publicly, so I'd genuinely love some feedback.

Does this solve a problem you actually have?

And if you've tried it, I'd especially like to know:

• What's confusing?
• What feels unnecessary?
• What's missing?
• Would you actually keep using something like this?

I'm much more interested in hearing what sucks about it than hearing that it's great 😅

Hey everyone,

I launched SlideSieve on Product Hunt today. Honestly I've had the launch ready for almost a month but kept putting it off because I was nervous about putting my work out there. Finally hit the button today.

I take a lot of online courses on DLAI, Coursera, Udemy, YouTube, etc. Whenever I'm watching a lecture, I want to save the slides for later. The problem is that manually screenshotting kills the flow: you're constantly pausing, snapping a screenshot, trying to avoid catching the video player UI. And you still end up with a messy folder of images, or miss a slide and have to scrub back to find it.

That's the problem SlideSieve is meant to solve. It's a browser extension that runs in the background and captures slides automatically while the video plays, so you don't have to pause.

A few things I built into the capture logic to make it actually usable:

• Skips frames where the instructor's face fills the screen
• Ignores code, terminal windows, and dark transition screens, so it only grabs actual slides
• Exports everything as a clean, ordered PDF once you're done

Product Hunt has a lot of big platforms promising to change everything. This isn't that. It's not an AI "second brain," it won't take your tests for you. It's a small, focused tool to make studying a bit less annoying. There's a free tier to try it, and a one-time purchase for unlimited captures — no subscription, no cloud processing, everything runs locally in your browser.

Link if you want to check it out: SlideSieve on Product Hunt

Built this to fix my own studying mess. Nervous but glad to finally share it.

The idea was pretty simple: instead of treating a new tab as a blank page, make it a lightweight workspace.

I'm particularly interested in the UX right now.

The current version has:

• App shortcuts

• Bookmark collections

• Quick notes

• Tasks

• Focus timer

• Wallpapers

• Weather

• Designer/developer-focused widgets

One thing I deliberately tried to avoid was turning it into a giant widget dashboard. I want the interface to stay calm and useful.

For people who use New Tab extensions:

What feature makes you actually keep one installed?

And what usually makes you uninstall one?

I'm looking for criticism as much as compliments.

👉 Check Cosmos

AI is getting insanely powerful, and somehow harder to use.
Taku fixes the last mile. It turns the best skills, agents, and workflows into real desktop apps anyone can run, remix, and make their own. Borrow setups from the pros, skip GitHub and setup, or just tell Taku what you want and watch it assemble the stack.
The more you work, the more Taku learns what you need, and brings the right tools to you.

The observation behind it: AI was supposed to let us do less. Instead there's a thousand new things in the feed every day, each one asking you to learn its prompts, install its dependencies, read its docs. More tools than ever, and everyone's more tired than ever.

Someone already spent months tuning the setup you need. On Taku it reaches you as an app. Open it, it runs. Then change it: swap the goal, add your own context, point it at your work. You describe what should be different; you never touch the code.
Honest status: it's a Beta. The Mac app is available now, Windows is an experimental preview with incomplete integrations, and Intel Mac and Linux aren't there yet. Publishing your own Stax isn't open yet either. That opens progressively through the Beta.

Borrow brilliance, make it yours.

I built Munder Difflin, a free and open source desktop app (Electron) that runs a multi-agent harness locally on your machine. It wraps CLI agents you already have, Claude Code included, so your clone works with your actual setup instead of making you migrate anything. It supports 10 CLI agent providers off the shelf.

What it does: you give it your workflows and it runs them on your machine while you’re away. Talk mode lets you orchestrate by voice, MemPalace gives agents a shared memory so they hand off work to each other, and Slack and webhook triggers let you kick off runs remotely.

How Claude Code helped: I built basically the whole thing with it. 300+ commits on the repo are co-authored by Claude. It did the Electron scaffolding, most of the agent orchestration layer, the process management for keeping long-running agents alive, and a lot of the refactors when I went from supporting one CLI provider to ten. The voice orchestration in Talk mode was almost entirely Claude Code sessions.

It’s free. Read the repo or grab the build from GitHub, no account, no key required beyond whatever CLI agent subscription you already have. I’ll add repo in comments

Happy to answer questions about the architecture.

I really like Wordle, but the one thing that always bugged me was that there isn't actually an opponent.

You're basically racing your own past performance.

So I built LOUTRIS — basically Wordle, but as a live competitive 1v1.

Both players are solving the same word, but they share a pool of 7 guesses total, split 4–3 between them.

Each player also gets 90 seconds on their own clock, chess-clock style. Your clock only runs while it's your turn and stops as soon as you submit a guess.

So now you're not just trying to solve the word.

You're trying to solve it before your opponent does, while managing your limited guesses and your own time.

Whoever gets the word first wins.

There’s also:

-ELO rating

-Global leaderboard

-Wins / losses / draws

-Daily Word mode + streaks

-Classic mode

I built the whole thing solo and it's still evolving. The design definitely needs some work, but I'm pretty happy with how the gameplay feels so far.

If you want to try it:
https://loutris.online

Would love to hear what you think, especially about the 7 shared guesses + 90-second chess clock idea.

Hey, everyone. I am Matheus Araújo, from Brazil, and I have been building Yrkit for the last few years. It is an IDE that works on the cloud currently - I have plans for it -, and has some cool features: live preview, code editor, console, elements (like devtools), terminal, ssh, kanban, drop-and-drop, ai, and other tools.

I still don't know how to distribute it, and I still have no one using it except myself - I use it daily for my clients' projects -, and I would like your feedback.

Yrkit is a dream of mine, I always wanted to have an IDE that I build myself, as well as a programming language that operates with it - yr, at https:yr-lang.org. It is a working product, I already launched it, and I am experimenting marketing and distributing, but I would really love your feedback.

For me, it works because I can code from anywhere, and it is perfect for JS and Node. I code from my phone, wherever I am at, and, if I have to do some things in the terminal, I can access it directly, ou go through my computer and run the actions that it created. It generates artifacts in html, css, js, bash, python, etc.

I still don't know how to pass that idea to other people, or how to talk about this project, but I would really love some feedback, and I would love to have someone else using it.

I appreciate all feedback.

Matheus Araújo

Over the past few weeks I've been building Gray Box — a small, local-first tool that acts as long-term memory for anything I'd otherwise forget (work notes, meeting takeaways, task owners, random ideas, personal stuff too).

The idea is simple:

1. Capture — dump whatever's on your mind, instantly, no structure required. This step does nothing clever on purpose — it just writes your text to an immutable inbox. Zero chance of losing an idea to a bug or a slow API call.
2. Organize — on demand, an LLM reads your unprocessed notes and extracts people, projects, tasks, decisions, meetings — then deterministic Python (not the LLM) creates/merges the actual wiki pages and maintains backlinks. The model only reasons; it never touches the filesystem directly.
3. Ask — query or chat with your knowledge base and get a cited answer pulled only from what you've actually captured. If it doesn't know, it says so — no hallucinated answers.

Why I built it this way:

• Plain Markdown + YAML frontmatter, no database. Every page is a .md file you can grep, diff, or read in any editor forever. If you stop using Gray Box tomorrow, your knowledge base is just a folder.
• No vector DB by default. At personal scale (hundreds–low thousands of pages), keyword search + a real link graph (related/backlinks, walked one hop during retrieval) handles almost everything. Embeddings are there if you want better recall, but they're opt-in, not a prerequisite.
• Immutable inbox. Your raw notes are never edited or deleted by the organizer. If the LLM mis-extracts something, your original words are always still there.
• Any LLM. Built on LiteLLM, so point it at OpenAI, Anthropic, Gemini, Mistral, or a fully local model via Ollama — one config value.

It also ships with a nice interactive TUI (arrow-key menu, file-import shortcut, workspace switching, live spinner during LLM calls) if you'd rather not memorize CLI flags — that's honestly become my favorite part of the project.

There's also a lightweight local dashboard for browsing your knowledge base, exploring backlinks, visualizing your notes as a graph, and chatting with your captured knowledge—all without leaving your machine.

Repo: https://github.com/Aaryanverma/graybox

pypi: pip install graybox

I'd genuinely love feedback — especially from anyone who's tried the "capture now, structure later" approach with other tools and has opinions on where it breaks down at scale.

It's not trying to be a "real-time collaborative team wiki" or a WYSIWYG notes app — it's aimed at one person's running memory of their own life and work, captured with as little friction as possible.

I recently launched a travel companion app called Roamer, and after building the product, I ran into a completely different problem:

How do you actually explain your product to people?

A normal poster could show the UI, but it couldn't explain the whole product.

I wanted to create carousels where every slide connected to the next and actually told a story.

I tried combining ChatGPT, image generators, and design tools, but I kept getting:

• disconnected slides
• inconsistent visual styles
• too much manual work
• lots of time spent fixing AI output

So I started building the tool I wished I had.

That's how StoryMint came together.

The idea is simple:

One rough idea → structured story → connected visuals → editable carousel.

You can plan the story before generating anything, review/edit the content, generate the visuals, regenerate individual slides, and then export the final carousel.

I've just launched it and I'm still very much in the stage of learning from real users.

I'd genuinely love feedback from people here:

Does this solve a problem you've experienced? What would you change or add?

If you want to try it:
StoryMint

And I also launched it on Product Hunt and peerlist if you'd like to check it out:
StoryMint on Product Hunt
Peerlist → Vote on Peerlist

Thanks - genuinely curious to hear what you think.