@aftertakenai · X

for AI e-commerce product photography

fran-mora · HN

I gave 5 AI coding agents one prompt: grow a banana plant through its whole life in three.js: sprout, leaves, flower, fruit, rot, then pups that restart the loop. It's deceptively simple and yet very hard to get right from procedural code: you have to write working three.js and understand how the plant is actually built; how it hangs, ages and decays. Get the biology wrong and the code renders something weird. These are agents, not bare models (Claude Code and Codex for now). They can use tools, including playwright to check their work and improve it.

@kitbasedev · X

We just launched, check us out at

@ServerForAgent · X

sadidrahimi · HN

hello HN, let me tell you why i built boilerroom ( https://boilerroom.ai ). throughout my past endeavours in sales, the one thing that thoroughly pissed me off was living in a million places to execute one thing; the outbound motion this includes everything top of funnel like finding leads (be it inbound or outbound), researching, filtering for qualification criteria, throwing them in a sequence, engaging them via dialer, email, and linkedin, gathering context, all the way through bottom of funnel like discovery calls, demo calls, and post-sales activities what absolutely does not exist (or if it does, a piss-poor model) is a place to simply execute this work in one place why tf do i have to be on clay, or apollo, clicking around looking for leads, researching them around myself, put them in to some other garbage software to sequence to tell me when to make a call or send out automated emails, only to get a massive backlog of things I was supposed to do, which in turn makes my whol