
Steve (Builder.io)
@Steve8708 • 137,160 subscribers
CEO @builderio - visually code together
Shorts
Videos

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.
Steve (Builder.io)5,333,975 просмотров • 3 дней назад

Announcing Builder 2.0 We raised $67M to build collaborative coding for Claude and Codex - Start tasks from a local branch, Slack or Jira - Real-time collab between humans and agents - 100s of parallel agents code, test, review Reply "Builder" and I'll DM you 500 agent credits
Steve (Builder.io)90,021,977 просмотров • 6 месяцев назад

Announcing the Builder Review Agent: in-browser testing of every PR Stop shipping broken code. Let agents verify every change actually works. • Clicks, types, and navigates • Covers critical flows, edge cases, regressions • Hands you findings, repros, & one-click fixes
Steve (Builder.io)22,032,263 просмотров • 5 месяцев назад

Jev is awesome but for the love of god please STOP posting fake demos
Steve (Builder.io)305,003 просмотров • 29 дней назад

Introducing /visual-edit - a skill to visually edit your local code like a Figma canvas - works with any agent or model - Figma-grade visual editing on your local apps - apply visual updates through your coding agent - multiplayer and collaborative - 100% free and open source
Steve (Builder.io)49,191 просмотров • 17 дней назад

Introducing Clips - 100% free, open source, agent-native alternative to Loom Unlike Loom, agent's can fully understand Clips just from a URL. Every Clip comes with APIs and metadata for agents to explore their contents. Agents can "see and hear" anything in a Clip - not just transcripts, but everything visually in the video at any timestamp. Easily share bug reports, feedback, analyses, or anything else in a way that you can easily pass to agents to use to improve products, reports, or more. Also unlike Loom, you own the software, so no one can jack up prices on you suddenly like Loom did to us. Clips is made to be customized. The built-in agent can customize its own code, so you can personalize the app to your needs and workflows. This, in my opinion, is the future of software. Open-source, forkable, customizable with agents, to make your own personal version of anything. You can also import Looms just from a URL and upload videos as well. I got so sick of telling people "don't send me feedback as looms, I can't pass those to agents, I need text and images" that I had to just solve this once and for all. There's a free hosted version you can use too, or fork and self host yourself. Will link to both in the replies.
Steve (Builder.io)233,736 просмотров • 3 месяцев назад

When I’m trying to improve the user experience of my applications, one of the most valuable things is being able to see an entire user flow as a storyboard. Not just one screen or screenshot at a time. This is something I love using the `/visual-plan` skill for. You can describe any flow you want, and the agent will look through your code and wireframe out a storyboard of what the flow looks like. Then you can visualize the steps in a simplified way and spot areas to improve. Recently, I found that in certain flows we were still asking for organizations, even though I thought I had gotten rid of that and made it automatic. A quick storyboard let me see all the different code paths in a simple, visual, intuitive way. Spot the areas of the flow I didn’t want. And have the agent fix it. Sign up, onboarding, and setup flows are usually some of the most important experiences in your app. And usually the least looked at. Especially because it can be hard to reproduce every flow, for every situation, for every user type, feature flag, or whatever else you have. The `/visual-plan` skill lets you visualize any part of your code. Either to understand the current state, plan out a new state, or recap updates that were made. I’m pretty addicted to this skill. I use it for a lot of other things too, so let me know if you want to see videos on those. And of course it’s all open source. You can grab it on my GitHub. I'll link to it in the thread. If you try it, let me know your feedback.
Steve (Builder.io)149,220 просмотров • 3 месяцев назад

Introducing Fusion 1.0, the first AI agent for the full product development workflow • Speaks product, design, & code • Lives in your stack • Learns how your team builds & self improves 10M designs & PRDs turned into real products & features for the worlds largest companies
Steve (Builder.io)391,617 просмотров • 11 месяцев назад

How I've changed the way I do code reviews by using the /visual-recap skill:
Steve (Builder.io)118,303 просмотров • 3 месяцев назад

Introducing /visual-plan - a skill to generate rich, visual plans for Claude Code and Codex. Plan mode in Claude Code is incredible. But I always find my eyes glazing over when it gives me this huge markdown essay in my terminal. I found I can make much better visual plans with reusable components. So I made a skill called `/visual-plan`. It generates plans as MDX with visual, interactive components. Diagrams, interactive API specs, schema design changes, annotated code, and even pan and zoomable wireframes. So for any UI work, you can look at a wireframe first, comment on it, iterate, and then have the agent work. I’ve found this to be a much more intuitive interface for reasoning about what the agent is doing. It’s somewhat inspired by that popular post about how HTML is better than Markdown. But HTML can be slow and verbose to write. And it doesn’t look good checked into a repo. This has really made me feel like humans and engineering are entering a new abstraction phase, where we reason about things at the plan level. As long as the plan is good, agents are getting more and more reliable at executing on it. Almost to the degree that we trust the C compiler to compile to assembly reliably. Plans are the new intermediate representation. I also made a skill for the reverse of this, called `/visual-recap`. After the agent works, it gives you a recap of everything it did. Same idea: wireframes, interactive API specs and diffs, schemas, annotated code, etc. So now when you’re reviewing what the agent did for you, or looking at a pull request of somebody else’s code, you can see a visual recap instead of just reading a wall of text. It’s all free and open source. You can find it on my GitHub. Will link to it in the reply because we all know how dumb these algorithms are with links.
Steve (Builder.io)126,758 просмотров • 4 месяцев назад

i made a website that is ai-generated as you browse it is this the downfall of the internet?
Steve (Builder.io)644,610 просмотров • 2 лет назад

Introducing Agent-Native mail: the Jev-powered inbox Tell it in natural language what you want to prioritize, filter, and categorize. Jev will manage your inbox for you, and delegate to agents to take action based on your rules, ultra fast. 100% free and open source
Steve (Builder.io)22,436 просмотров • 18 дней назад

i'm a little sick of chatgpt giving me obviously broken code i've found a "micro agent" approach to LLM code generation can work much better the LLM first generates a *test*, and then enters a loop where it generates and iterates on the code until the tests pass source below
Steve (Builder.io)544,371 просмотров • 2 лет назад

GPT-6 and Opus 5.5 make highly autonomous work cheaper than ever That makes now a better time than ever to build an autonomous software factory Here's a deep dive on how we now automated 90% of our development with self-governing agent factories Steal our /factory skills:
Steve (Builder.io)22,128 просмотров • 24 дней назад