Builder.io launches Agent Native beta for apps shared with AI
Builder.io launched Agent Native in beta on October 14, offering a TypeScript framework for apps that people and AI agents operate together. Developers can start locally with the framework or build online through Builder.io.
One operation across several interfaces
The action documentation describes defining an operation once in the app’s actions folder. React controls, the agent, HTTP clients, the command line, MCP and A2A then reach that implementation through supported interfaces. Each path runs shared validation and access checks, reducing the need to maintain separate integrations for human and agent users.
Builder says agents receive relevant interface context, such as the selected record or active view. Work done by either side remains available to the other. Its example apps include Slides for editable presentations, Design for interactive prototypes and Clips for screen recordings with transcripts and timestamped images.
The public repository identifies the project as MIT licensed. It documents PostgreSQL for production and PGlite for local development, with deployment on Nitro compatible hosts.
Approval and access are separate controls
The authorization guide makes an important distinction. A needsApproval setting pauses an agent call for human review before its side effect runs. That gate is off by default and applies to the agent loop. It does not replace authorization checks governing who may call an operation through the UI, HTTP or other interfaces.
Resource access policies and authorization guards are separate mechanisms. Developers must also scope database queries and writes to the records a caller may access. Public protocol exposure is off unless explicitly enabled. The documentation says mutating actions are audited by default, while read only actions are skipped unless configured otherwise. These are documented controls, not an independent security assessment.
The distinction between identifying an agent and authorizing its action also matters in Amex’s separate framework for agent payments.
What beta means for deployment
The stability policy says packages have not reached version 1.0. Minor releases may change APIs or behavior still in alpha or beta, while patch releases are intended for compatible improvements and fixes. Generated apps pin the framework version that supplied their template. The documentation recommends deliberate upgrades with migration tools rather than replacing that pin with latest.
A 1.0 release by the end of 2026 is a target, not a commitment. Alpha and beta stages provide no production support guarantee.
ByteForward read the announcement, repository and documentation. It did not install the framework, test integrations or measure performance.
Illustrative developer workstation photographed by Bijay Yadav, published by the WordPress Photo Directory in 2023 under CC0. The photograph does not show Agent Native.
