Builder.io (@builderio) header
Builder.io (@builderio) profile picture

Design to Shipped. Faster.

Joined November 2013
Photo by Builder.io (@builderio)Photo by Builder.io (@builderio)Photo by Builder.io (@builderio)Photo by Builder.io (@builderio)Photo by Builder.io (@builderio)Photo by Builder.io (@builderio)Photo by Builder.io (@builderio)Photo by Builder.io (@builderio)Photo by Builder.io (@builderio)Photo by Builder.io (@builderio)
The first Builder × Agent-Native hackathon is a wrap. Five winners, $10,000, and just 0.2 points between first and fifth. Every winning app had one thing in common. The AI takes the grunt work, and the important calls stay with you...
5
3
1
17
2,134
→ Groundswell by @Favour Olaboye. It boils 340 GitHub issues down to the problems that matter most. They won by building something you’d trust with your actual work. These five are just the start. Over the next few days we’ll feature more of what the community built.
1
221
→ Verbatim by @Yehor Ivashchenko. Put 500 customer reviews in and get the real themes out, in customers’ exact words. → Apprentice by @Arpit Singh. It learns how a maintainer handles GitHub issues, then starts doing the job for them.
1
190
→ Muscle Memory by @Evgeny Vinokur, our grand prize winner. Show it how to handle a support ticket once, and it takes every one like it from there. → Eighty by @Oluebube Chukwu. Snap a photo, record a voice note, and your Medicaid work-hours paperwork gets done.
1
259
Please stop handing your AI agents your API keys. I know, I'm guilty too. My agents run as me, with my GitHub token and the keys in my .env files. But there are better ways now. I'm slowly switching over. I wrote up what they are, and why attackers spent October going after keys like mine. builder.io/blog/ai-agent-ide…
1
6
9
1,701
Builder.io retweeted
Wrote a piece on building apps for both humans and agents by defining the function once. Schema, validation and permissions live in the action, and every surface (UI, agent, HTTP, MCP, CLI) calls it. builder.io/blog/ai-agent-act…
8
5
11
6,229
If an agent can rebuild your app in a few weeks, what are your customers actually paying you for? I don't think it's lawyers. A clone gets graded on matching the original, bugs and all, so the best it can do is tie. I wrote up what I'd build instead, and why we made all of Agent-Native free to fork: builder.io/blog/the-best-a-c…
2
3
9
1,222
Thanks to GrokBot, I merged more PRs last week than ever before. And also, I'm not gonna keep using it. My 16 bots stayed up all weekend while I slept, burning $100 deciding they had nothing to tell me. On Monday, when I actually needed them, they were out cold. GrokBot is still the closest thing we have to a working always-on staff. It's just not there yet, and the reasons are architectural. Here's what happened, and what I think always-on agents actually need. builder.io/blog/grokbot-revi…
3
5
797
Introducing Agent-Native: an open-source framework for building agentic apps. Agents love walls of text. But humans don't. An agentic app let's you interact with agents through a visual interface. Engage with agents visually, via text, or both at once. Now in beta.
84
101
30
2,085
5,341,841
The least productive thing I can imagine doing is watching an agent work. But I still do it, because I'm never really sure if the agent understood what I wanted it to do. So I end up reading the tool calls and watching files change. I want to agree on what it's gonna build, leave it alone, and review what comes back. But an all-text plan that's several pages long just feels like homework, and it's easier to let the agent run, even if it wastes tokens, just so I can see the result. What I need is a better way to verify the plan and review the result, just at a glance. Something where I can see the layout or the API flow and point to the part that's wrong. Here's what I've been doing instead lately. builder.io/blog/stop-watchin…
5
15
2,115
I keep getting frustrated when I ask an agent to clean up some code and get another wrapper, another helper, and all the original complexity still sitting underneath. Then I have to figure out if anything actually got better. We’re running into this at Builder while developing Agent Native pretty much as fast as we can. People leave feedback in Slack, and an agent factory picks it up and works on it. A lot is changing, all the time. So validation is a big deal for us. In one cleanup experiment, an agent removed a lint warning, passed typechecking, and passed all 23 tests in the focused suite. The code still used unvalidated input. Everything passed, but we still hadn’t checked the behavior we actually needed. I wrote up what we’re learning about asking agents to clean up code, figuring out what needs to change, and checking whether it actually got better. builder.io/blog/de-slop-ai-g…
3
6
1,150
Live now. Building a plan from scratch, reviewing a real PR, triaging a ticket — all in Plans. free and open source → luma.com/plans
1
1
7
2,018
Sept 15: we build a plan from a blank prompt, review a real PR the same way, and triage a ticket like an agent would. 20 min, and a free, open-source tool you can use today → luma.com/plans
4
1,157
Introducing /webmcp - make your agent workflows visual
6
12
1
173
15,592
Plans turns your coding agent's plan into wireframes, diagrams, and annotated code you can actually review. Comment on any block, the agent revises. free and open source. live demo sept 15 → luma.com/plans
1
2
839