Builder.io launches Agent-Native, an open-source TypeScript framework for building Agentic Apps. * 8 hrs ago "Builder.io launches Agent-Native, the free, open-source TypeScript framework for building agentic apps, now available in beta."Now in beta, Agent-Native enables developers to build AI agents with interactive UIs that share actions, data, and application state. SAN FRANCISCO, October 14, 2026 -Builder.io today launched Agent-Native in beta, a free, open-source TypeScript framework for building agentic apps. An agentic app is an AI agent with the intuitive interface of an app. The agent and UI work as one, sharing the same actions, data, and application state. Anything a person can do in the app, the agent can do too. AI agents make it possible to describe an outcome and delegate the steps, but chat interfaces alone make it difficult to inspect results, refine work, and collaborate. An empty prompt box also leaves people guessing what an agent can do, while powerful AI workflows often remain limited to the individuals who created them. Many workflows need intuitive interfaces that make an agent's capabilities visible and let people see, steer, and refine its work. Agent-Native provides developers with an open foundation for building AI agents with interactive UIs. People can delegate work through natural language, see and refine results directly in the interface, and take control whenever they need to, without being tied to a single AI model or proprietary platform. "Every kind of work has an interface that helps people do it, and agents shouldn't take that away," said Steve Sewell, CEO of Builder.io. "With Agent-Native, the agent and the app are equal partners. You can hand work to the agent, see the result right away, and take control whenever you need to." One Framework, Shared Actions Across Six Surfaces Agent-Native connects the agent and UI through three shared foundations: actions, data, and application state. When a person makes a change in the UI, the agent has access to the updated information and relevant context. When the agent completes work, the results appear in the app for people to inspect, refine, and share. Rather than building separate functionality for agents and user interfaces, developers define each action once. Agent-Native makes those actions available through six surfaces: the UI, agent, HTTP API, CLI, Model Context Protocol (MCP), and Agent-to-Agent (A2A) protocol, using the same validation, permissions, and implementation. Unlike computer-use agents that navigate software by clicking through interfaces, agents built with Agent-Native call the same actions the UI uses. This approach can reduce unnecessary steps and token consumption while enabling agents to complete work directly. Agents can also run on schedules, respond to events, and work with connected tools. An Open Foundation for Agentic Apps The Agent-Native beta includes: * Shared actions across six surfaces: Define capabilities once and make them accessible through the UI, agent, HTTP API, CLI, MCP, and A2A. * Connections to tools and other agents: Connect external services through MCP and expose capabilities through A2A, with advanced agent-to-agent connections in alpha. * Built-in agent and team capabilities: Instructions, skills, memory, scheduled tasks, authentication, permissions, and collaboration features. * Support for multiple AI models: Bring an API key for Anthropic, OpenAI, Google Gemini, OpenRouter, or any OpenAI-compatible endpoint, or run a local model with Ollama. * Optional Agent-Native Toolkit: Ready-made building blocks for editing, collaboration, version history, and application setup. Builder.io has also built three open-source agentic apps using the framework: Clips for capturing and working with screen recordings and voice notes, Slides for creating and refining presentations, and Design for generating and editing interactive designs. These apps, currently in alpha, demonstrate how Agent-Native can power different workflows, with agents and intuitive interfaces working together. As AI makes software easier to inspect, copy, and rebuild, competitive advantage increasingly shifts toward how quickly teams can build and customize tools for their own workflows. By making Agent-Native free and open source, Builder.io gives developers a foundation they can extend, personalize, and deploy using their own models and infrastructure. Availability Agent-Native is free, open source, and available in beta today. Developers can start locally with the TypeScript framework using: npx -yes @agent-native/core@latest create my-agent -standalone -template chat Agent-Native supports PostgreSQL databases and deployment to Node.js environments and platforms including Vercel, Netlify, Cloudflare, and AWS. Developers can bring their own AI models, tools, and infrastructure while retaining ownership of the applications they build. Teams can also build agentic apps online with Builder.io, with building, hosting, database, authentication, and deployment handled by the platform, without local setup. About Builder.io Builder.io is a collaborative platform for building with AI agents. Teams use Builder.io to build, review, and ship software, from agentic apps with rich, intuitive UIs to new projects and features in existing codebases. The company also created Agent-Native, the free, open-source TypeScript framework for building agentic apps. Builder.io is based in San Francisco. Learn more at https://www.builder.io. Media Contact Contact Person: Geoffrey Taft Phone: 415-275-0615 Address:95 3rd Street, 2nd Floor City: San Francisco Country: United States Media gallery

Builder vs Lovable - what is the right tool for your stack. Posted on March 13, 2026 in Lovable Modern development tools promise to help teams build faster, but they often solve very different problems. Builder.io and Lovable.dev are frequently compared because both aim to simplify product creation and reduce engineering friction. However, they operate at completely different layers of the development process. Understanding how they differ can help teams choose the right tool for their workflow - or even combine them effectively. What Builder.io is designed for. Builder.io is primarily a visual development and content management platform. It allows teams to visually design pages and manage content while integrating with existing frontend frameworks like React, Next.js, and Vue. The platform is built to help designers, marketers, and product teams update UI and content without requiring developers to modify code constantly. Builder.io is commonly used for: * Marketing websites and landing pages * Content-heavy product sites * Visual editing of UI components * A/B testing and conversion optimization * Managing content in a headless architecture Instead of generating entire applications, Builder.io works on top of an existing codebase. What Lovable is designed for. Lovable takes a different approach. It is an AI-powered full-stack application builder that generates complete applications from natural language prompts. Rather than editing an existing product, Lovable can create the entire structure of an application - including frontend components, backend logic, data models, and integrations. Teams often use Lovable for: * Rapid MVP development * Building internal tools * Creating SaaS products quickly * Generating APIs and backend workflows * Iterating on product flows with AI assistance Lovable focuses on turning ideas into working software as quickly as possible. Frontend editing vs full-stack creation. The biggest difference between Builder.io and Lovable is scope. Builder.io focuses on visual control of frontend experiences. It allows teams to design, edit, and manage content inside an existing product. Lovable focuses on generating the product itself. It helps teams move from concept to functioning application without manually wiring every piece of the stack. In simple terms: Builder.io improves an existing product. Lovable helps create a new product. When Builder.io makes sense. Builder.io works best when: * Your product already exists * You want designers or marketers to control layout and content * Your team uses a headless CMS architecture * Landing pages and marketing pages change frequently * Conversion optimization is a priority For teams that already have a development stack in place, Builder.io can reduce dependency on engineering for everyday content updates. When Lovable makes sense. Lovable works best when: * You are starting from an idea * You need to build an MVP quickly * Your team has limited engineering bandwidth * You want to test product workflows fast * You need internal tools or operational software Lovable accelerates the earliest phase of product creation, where speed and experimentation matter most. How teams can use both. In some workflows, these tools complement each other rather than compete. For example: * A team uses Lovable to generate the core application and backend logic * The product becomes functional and usable * Builder.io is introduced to manage marketing pages and content experiences This combination allows teams to build the product quickly while maintaining strong visual control over public-facing pages. The real difference is where they fit in the stack. Builder.io and Lovable represent different philosophies of modern development. Builder.io focuses on improving the design and content workflow around an existing application. Lovable focuses on accelerating the creation of the application itself. Both tools remove friction, but they do so at different stages of the product lifecycle. Conclusion. Builder.io and Lovable are built for different moments in the development process. Builder.io helps teams design and manage frontend experiences efficiently, while Lovable helps turn ideas into fully functioning applications with minimal setup. Choosing the right tool depends on where you are in your product journey. If you already have a product and need better control over content and UI, Builder.io can help. If you are starting from scratch and want to build quickly, Lovable provides a powerful starting point. Your email address will not be published. Required fields are marked *