@greenlinebudget · X

financial tool for startups:

@GenesisAIApps · X

A smart AI copilot ecosystem for life, work, and beyond the stars.

u/alexkendig · Reddit

I got tired of paying monthly for X tools, so I built a BYOK/Local browser extension instead Hey everyone, I use X/Twitter to share product updates, find customers, and build an audience. The problem is that most X tools eventually become another expensive subscription. TweetHunter, Typefully style tools, schedulers, AI assistants, outreach tools, it adds up quickly, often $30–$90/month. So I built Tweetback, a browser extension workspace for X that uses your own AI key in

u/surmado_rachel · Reddit

We built a cheaper code review tool for small teams We've been working on a code review tool for small teams, solo founders, and vibe coders who want a second set of eyes on every PR without paying Claude-level prices. The idea is simple: Surmado's Scout reviews your PRs against your own standards, not random generic lint rules. You add a STANDARDS.MD file, and on every push Scout gives you: What looks good/What needs work/A short reviewer brief so a human knows where to focus/Feedback

@__singhritwik · X

@duke_can_c_u · X

Hi I’m the founder of a content collaboration platform for teams and creators, with focus on editorial workflows. Always looking to connect with people passionate about content, SaaS, and building great products.

@sykatt01 · X

Here it is: Definitely appreciating feedbacks

@collinsvidzro · X

othmanosx · HN

I still don't like the fact that AI is adding more stuff for us to read, it's accelerating the code production but slowing down the code review. I built my own code reviewer as well ( https://pyor.review/ ), surfacing the important stuff first is the right track, but adding more stuff to read is daunting, but asking AI to just point you to what you need to focus on and skim the noise is what I'm leaning more towards.

@adnaanazam · X

Build for no code dynamic screen

@joffreyio · X

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