
vilano ai
15 posts



I built an AI selection committee that argued its way through March Madness. Not one prompt. A real process: - team dossiers - matchup hearings - red-team rebuttals - challenger brackets - final selection - full replay Built on @vilano_ai Runtime.


One underrated benefit of building a tiny DSL around an agent runtime (@vilano_ai), you can encode behavior.


Advisory convo this week w/ someone who’s seen a lot of real companies get built. Showed him Wilbur + Corpus (@vilano_ai) Him: “Super powerful, how far along?” Me: “Core’s basically done.” Him: “Dude… most people raise way before this.” Whoops 😅

Hot take: coding agents are nearing their limit. The next leap of capability is not at this layer. @vilano_ai is building Wilbur and Corpus to fix this. Even in their infancy, they’ve made me far for capable than I could have imagined and we haven’t even raised money yet.


reminder that almost half of swe-bench verified is only django

My dev setup feels like cheating. Ephemeral envs spin up per branch, tied to Git as the source of truth, artifacts in S3, and AI agents ship the PRs with me in the loop.

