@StateSync_ · X

@CoderLuii · X

A machine for your coding agents.

@DaiwikShashi · X

Building Scribur — the operating system for in-house UGC teams. We help in-house teams manage campaigns, content ideas, scripts, submissions, revisions, approvals, creator communication, and performance tracking all in one place.

@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

not_wowinter13 · HN

Unified workspace where AI knows your business

u/OGMYT · Reddit

Validating a micro-SaaS for checking AI-built software before it ships I am building **Flows**, a system that turns an AI software goal into ordered implementation steps, checks, repair prompts, and a build report. The business thesis is not “better prompts.” It is reducing the cost of getting from an AI-generated first draft to a checked, shippable result. Metrics I want to measure: - prompts per completed project - tokens or credits per checked step - first-pass check rate - repair atte

@iamdebiddo · X

@computer_agents · X

@iPranayJoshi · X

Would be honoured to come join! Built talk about vibe coding at

@mfranklindesign · X