Build React apps on the Headless 360 platform using Salesforce Multi-Framework. Whether you prefer to code by hand or speed up development with Agentforce Vibes, now you can create, test, and deploy React apps for both consumers and enterprises. This feature, now generally available, includes some changes since the last release.
Where: This change applies to Lightning Experience in Enterprise, Performance, Unlimited, Developer, and Partner Developer editions hosted on Hyperforce where English is the default language.
When: This feature is available starting June 3, 2026.
Why: Use Agentforce Vibes with Salesforce Multi-Framework to jump-start React app development with ready-to-use templates and sample apps. Add features including search, authentication, CMS images and branding, and the Agentforce Conversation Client. Or if you prefer to code by hand, you can use familiar Salesforce DX workflows, CLI commands, and project structures to manage React apps alongside other Salesforce metadata.
Since the previous release, we:
- Added support for production and developer orgs.
- Introduced the Salesforce app domain for internal React apps.
- Improved app management in Setup.
- Added app access control via user profiles and permission sets.
- Updated the way employee-facing apps are rendered in the App Launcher. Now, the CustomApplication metadata type combines with UIBundle to control app visibility.
How: Salesforce Multi-Framework is now automatically enabled for orgs. For internal React apps, such as apps for employees signing in with their Salesforce credentials, make sure that the Salesforce app domain is enabled. From Setup, in the Quick Find box, enter Salesforce Multi-Framework, and then select React Development with Salesforce Multi-Framework. If you see the Enable Domain button, click it and confirm your change. If not, the domain is already enabled.
For previous beta participants, the metadata required for an internal, employee-facing React
app has changed. Previously, only the UIBundle metadata type was required and you set the
target field to AppLauncher to make the app appear in the App
Launcher. Now, you must:
- Set the value of the UIBundle's
targetfield to the newCustomApplicationvalue instead. - Include a CustomApplication metadata type and set the new
uiBundlefield to reference your app.