Builder.io

Design to Shipped. Faster.

[Pratham @Prathkum]

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.

https://t.co/heN30mvnlZ

[alice alexandra moore @tempoimmaterial]

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:

https://t.co/EoiAhS4r9d

[alice alexandra moore @tempoimmaterial]

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.

https://t.co/ixxrsm9Uij

[Steve (Builder.io) @Steve8708]

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.

[alice alexandra moore @tempoimmaterial]

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.

https://t.co/YzyQPHzy9F

[alice alexandra moore @tempoimmaterial]

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.

https://t.co/R3pGlHsrvG

[Builder.io @builderio]

Live now. Building a plan from scratch, reviewing a real PR, triaging a ticket — all in Plans.

free and open source → https://t.co/HErwjviHee

[Builder.io @builderio]

Tomorrow. Watch a coding agent's plan go from a wall of markdown to something you can actually review.

free and open source → https://t.co/HErwjviHee

[Builder.io @builderio]

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 → https://t.co/HErwjviHee

[Steve (Builder.io) @Steve8708]

Introducing /webmcp - make your agent workflows visual

[Builder.io @builderio]

free & open source → https://t.co/UmVGBOPIbi

[Builder.io @builderio]

A prompt box hands you a deck. An agentic app hands you one that builds itself.

[Builder.io @builderio]

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 → https://t.co/HErwjviHee

[Builder.io @builderio]

free & open source → https://t.co/UmVGBOPIbi

[Builder.io @builderio]

Tired of prompting the same fix five times? with slides you ask once, then edit anything by hand or in code.

[Builder.io @builderio]

free to try, open source → https://t.co/UmVGBOPIbi

[Builder.io @builderio]

You shouldn't have to talk to 100 people to build one deck. Connect your sources — Slides builds it on-brand, and because it's an agent, you can prompt it to rebuild itself on any interval you'd like.

[Builder.io @builderio]

Reading your coding agent's plans is rarely part of the plan. It's a wall of markdown in your terminal, gone the second you approve it.

There's a smarter way to work. free, open source. live demo sept 15

->https://t.co/HErwjviHee

[Matt Abrams @zuchka_]

Loom records the crime scene.

It doesn’t collect the fingerprints.

Agent-Native Clips records the bug AND captures console errors, failed requests, and status codes from the same session.

Free. Open source. Built for humans and coding agents.

[Builder.io @builderio]

Gamma creates a decent deck fast. Then you're in its canvas, on its subscription, hitting regenerate when it's 85% right. Agent-Native Slides is free, open source, knows your brand, and lets you edit anything. See it live Sept 1.
https://t.co/qr7MK7rOMh