@daicandev · X

Building proven, the tool that gets your product from idea to growing income

@Number1AIFanboy · X

I got to go to bed. More coding tomorrow. I just had a realization that I'm building cool shit, using @grok in an app that I built with Codex and refined with Grok. And now Grok just works on himself. LFG🚀 Drop me a note here: Get the app here (use LAUNCH50):

@akshay_nocode · X

Not exactly — Sentry captures errors, BugOps acts on them. It reads the Sentry alert, checks recent commits, traces root cause, and opens a fix PR. Think Sentry as the sensor, BugOps as the on-call engineer that never sleeps.

@9to5_Dad · X

Ai mobile app ui designer with taste

u/Zyron_X · Reddit

I built a service for people to use Codex API without 5-hour limit disruption I built a small service for people who use the OpenAI Codex API regularly and want more predictable usage without the 5-hour or weekly limits. It currently provides: Frontier OpenAI models (GPT 5.6 family included) Managed API key Monthly usage budgets depending to plan No 5-hour limit No weekly limit Under the hood, it is built on top of an open-source project and proxies requests to

@Ex3NDR · X

Few days ago Happy had a birthday. Tried to refresh one of the most neglected part of it: our Happy Website: also i built a new harness called “rig”. i started to use at work recently instead of codex/claude code and i liked how it does work. i want to share this with everyone. it is a codex and cause code reimplemented using Pi, but keeping native prompts and expanded a little for uniformity (like added workflows to codex yay!). when something new released that is worthy of porting - i ask Sol to mim for prompts or read sources directly and i can have a feature within an hour. why this is needed? i was constantly blocked by the needing of integrating a lot of models together, which each has their own harness or many doesn’t have any, but i didn’t want to go too far from native and don’t like the idea of extensions - i want experience to be the same everywhere. i think configuration > extensions. more soon

jayaprabhakar · HN

I've been building an open source formal methods system (fizzbee.io) for the past few years. Today I'm launching a new app built on the same technology. It performs requirements engineering using formal verification to uncover gaps and produce precise instructions for your coding agents to follow. When given a prompt, it - asks high signal follow-up questions - converts to formal spec and identifies complex requirements gaps - generates validation scenario At the end, it produces a specification document that can be shared with coding agents. In my trials on various projects, it produces working code in fewer iterations. Please give it a try and share your feedback. https://fizzbee.ai/ You can also look at a sample project. https://fizzbee.ai/projects/94bf2869-97a1-445c-8f5d-4445848b...

u/Still_Amphibian545 · Reddit

almost launched a side project with my api keys sitting in the repo (a week free gpt 5.6 on us) was about a day from launching a small project when i noticed my openai key was just sitting in a committed file. it had been there for weeks. no idea how i missed it. made me wonder what else was wrong that i couldn't see. turns out for vibecoded stuff it's usually the same handful of things. secrets in the repo, endpoints with no auth, a database with no access rules, no limit on the ex

Aldasams · HN

Show HN: DocFlow – AI documentation updates for GitHub pull requests

u/Administrative_Egg78 · Reddit

I built this because AI was making me a dumb&lazy engineer I noticed something sad about how I use AI. I was shipping faster, but practicing less. I could get answers quickly, but I was losing the habit of working through the fundamentals myself. So I built Unrot: short daily challenges for developers across languages, system design, architecture, data engineering, and other tracks. Game/xp and rewards system, a tiny bit competitive. No signup required to try it: https://unrot.dev

@itskalenai · X

stop writing bad prompts. #ai #claudecode #vibecoding

@BotariaDotBot · X

This Tuesday I'm launching Botbugger on @ProductHunt 🚀 One AI reviewer gives you 10 "critical" bugs — half hallucinated. So I built two: Claude Code + Codex review your code independently, then cross-check each other. Real bugs with fixes, not noise.