At TDX 2026, Salesforce introduced Headless 360: a way of exposing the platform's data, workflows and business logic as APIs, MCP tools and CLI commands. For teams that have built mostly inside the Salesforce UI, it's a significant shift, and it raises practical questions about skills, architecture and governance.
Salesforce behind any interface
Headless 360 is designed so Salesforce can power experiences outside its own screens, including custom React front ends and a new experience layer for surfaces like Slack and voice. Business logic and the security model stay in Salesforce, while the interface can be whatever your users need.
Built for coding agents
Salesforce announced more than 60 new MCP tools and 30 preconfigured coding skills, so AI coding agents such as Claude Code, Cursor and Windsurf can work with platform data and metadata directly. Paired with Agentforce Vibes 2.0, AI-assisted development becomes a first-class way to build on Salesforce.
DevOps moves closer to natural language
DevOps Center is now accessible through MCP, and natural-language DevOps lets teams describe deployments rather than script every step. That speeds up routine work, but it makes release governance more important, not less.
What doesn't change
Permissions, sharing rules, compliance controls and good data design still decide whether a solution is safe and maintainable. Headless access makes weak security models more visible, so review profiles, permission sets and integration users before opening the platform to new interfaces and agents.
How to get started
Pick one experience that is awkward in the standard UI today, such as a partner portal or a field workflow, and prototype it on Headless 360 with a small team. Establish coding standards, review rules for AI-generated code and a release path through DevOps Center before scaling up.