• Salesforce Headless 360 exposes Salesforce capabilityas an API, a Model Context Protocol (MCP) tool, or a CLI command, so people andAI agents can act on Salesforce data without opening the Salesforce UI. It wasannounced at TDX on April 15, 2026 and substantially expanded on August 19,2026.
• The rollout has shipped 60-plus MCP tools, 30-pluspreconfigured coding skills, a library of over 100 reusable Skills, theHeadless 360 and Data 360 MCP Servers, a Headless Experience Layer, and a setof agent testing and observability controls.
• Lightning Experience, Experience Cloud and browserworkflows are not going away. Headless is an added path, not a replacement.
• Agents that run headlessly inherit your existingpermissions, sharing rules, field-level security and approval chains. You donot rebuild the trust layer.
• Best starting point: one high-volume workflow withclear rules, a small idempotent tool set, and scoring evals defined beforelaunch.
• US context: Salesforce data shows the average number ofactivated agents per organization rose nearly 3x over the past fiscal year, andthe average agent now acts on six skills, up from two.
• SaasWorx designs and deploys Agentforce and headless Salesforce architecturesfor US teams, with 15-plus Agentforce implementations delivered and agentstypically live in about five weeks.
Salesforceco-founder Parker Harris put the question plainly earlier this year: why shouldyou ever log into Salesforce again? It reads like a provocation. It wasactually a roadmap.
For 25 years,using Salesforce meant working inside Salesforce. A rep opened a console,clicked into a record, updated a field. That model assumed a human at akeyboard. AI agents do not click. They call APIs, invoke tools and runcommands. So Salesforce spent two and a half years rebuilding the platform fora second kind of user, and shipped the result as Headless 360.
This guidecovers what has actually landed across the 2026 rollout, how it differs fromthe way most teams build on Salesforce today, which AI tools connect to it, anda sequence you can follow if you are starting from zero.
SalesforceHeadless 360 is an architectural change that makes every major Salesforcecapability available as an API, an MCP tool, or a CLI command. The browserinterface becomes optional. Humans can work from Slack, Microsoft Teams,WhatsApp or a custom React app, and AI agents can reach the same data,workflows and business logic directly, at machine speed.
The namecarries two ideas, and both matter.
• Headless means the front end is decoupled fromthe back end. Salesforce still holds the data, automation, permissions andworkflows. The interface is built separately, in whatever framework your teamprefers, and connects through APIs.
• 360 means the full estate is in scope: Data 360for context, Customer 360 for business logic, Agentforce for agent building andgovernance, Slack for engagement, and Tableaufor insight.
One point getslost in the noise. Headless 360 is not a new product you buy and switch oninstead of Salesforce. It is a different way of reaching the Salesforce platform you already run.
Headless 360has not landed as one release. It arrived in waves, which matters if you arescoping a project against what is genuinely available today rather than whatwas announced on a keynote stage.
A usefulcaveat for planning. The core package, including the Salesforce MCP packageand the agent CLI commands, has been available since April, but some toolsetsremain in Beta or Developer Preview and capabilities continue rolling out.Check the Salesforce CLI release notes for current GA status before you commita delivery date to anything.
Salesforcereleased more than 100 new tools and skills across the rollout. Here is whatdeserves your attention, grouped by the problem each piece solves.
Your codingagent gets live, governed access to your org: data, workflows, business logic,metadata. Developers can point Claude Code, Cursor, Codex or Windsurf at a realenvironment instead of working from stale documentation and guesswork.
MCP is worthten minutes of your architect’s time. It is a standard protocol that lets an AImodel discover and call external tools, APIs and data sources at runtime. Anycompatible client can talk to any compatible server without bespoke integrationcode. That is the difference between one connector per tool and one protocolfor all of them.
This is thepiece most summaries skip, and it is the most interesting architectural decisionin the release. Salesforce had a scaling problem: exposing thousands ofplatform features as thousands of individual MCP tools would force a model toreason across thousands of tool descriptions before doing anything useful.
So theHeadless 360 MCP Server presents an agent with four tools rather thanthousands, backed by a continuously growing library of skills. The agent’ssurface stays small and stable while the action surface scales independently. Adiscovery tool runs a semantic search across an index of every generated APIand skill and returns a ranked shortlist, so agents spend fewer calls huntingfor the right capability.
The practicalread: tool sprawl is a real failure mode in agent design, and Salesforce hasengineered around it at the protocol layer. If you have built your own MCPsurface and watched an agent flail across forty tools, this is the pattern tocopy.
Some workneeds more than a text reply. A card to approve. A rebooking flow to complete.A decision to record. The Experience Layer separates what an agent does fromhow it appears, so rich interactive components render natively inside Slack,and across mobile, ChatGPT, Claude, Gemini, Teams, or any client that supportsMCP apps.
Build thelogic once. Render it where your people already work. For a US business running support in Slack, this is the difference between a deflection experiment and a workflow the same distinction we drew when looking at how SaaS companies automate onboarding and supportdeflection with Agentforce.
Shipping anagent is easy. Trusting it eight weeks later is the hard part, because agentsare probabilistic rather than deterministic. They do not behave identicallyevery time. There is no bug to fix, only behaviour to observe and tune.
• Agent Script lets you define which parts of anagent’s behaviour must follow explicit business logic and which parts canreason freely.
• Testing Center surfaces logic gaps, policyviolations and inconsistent outputs before real users see them.
• Custom Scoring Evals score whether the agentmade the right decision, not just whether it ran. You set the standard for youruse case.
• Observability and Session Tracing show why anagent did what it did, so drift gets diagnosed in hours.
• A/B Testing runs multiple agent versions againstlive traffic so promotion decisions rest on data.
Mostenterprises will not run one vendor’s agents. Agent Fabric brings agents fromacross platforms under one governed control plane, with deterministic orchestrationand centralised governance of agents, tools and models. If you are stilldeciding which platforms belong in your estate at all, our comparison of Agentforce and Microsoft Copilotcovers that choice before the governance question arrives.
Teams thatwant full control of the visual layer can now build custom interfaces in React,with native Salesforce authentication, security and governance runningunderneath. Any design language, any interaction model, your brand rather thana themed portal.
Naturallanguage DevOps means you describe what to deploy and let the agent execute it.Salesforce reports that consolidating a build loop which previously spannedfour tools has cut cycle times by as much as 40%. Agentforce Vibes 2.0 bringsthe same capability natively inside Salesforce, with full org awareness andmulti-model support including Claude Sonnet and GPT-5.
Themarketplace now carries 10,000 Salesforce apps, 2,600-plus Slack apps, and over1,000 Agentforce agents, tools and MCP servers from partners including Google,DocuSign and Notion. Salesforce also opened a $50M Builders Fund for partnersscaling on the platform.
Both modelsare valid. The question is which one fits the workload in front of you.
The trap isthinking you must choose once, for everything. Most US organizations we workwith end up running both, with headless applied to two or three workflows wherethe payoff is obvious.
Adoption datagives useful cover for the business case. The 2026 Salesforce AgenticEnterprise Index analysed Agentforce usage from February 2025 to April 2026 andfound the following.
• The average number of activated agents per organizationrose nearly 3x over the fiscal year, and the average time from provisioning tofirst agent creation fell 53%, to around two days.
• The average agent now acts on six distinct skills, upfrom two at the start of 2025. During peak retail season, that figure reachednine, a 350% increase.
• Escalation rates from AI agents to human agents heldsteady at 32% even as volumes grew, and agents resolved seven of every tenservice chats without human help.
• Retailers that deployed agents during the holidayseason saw a 4x higher sales growth rate, at 8% year over year against 2% forthose without — a gap we unpacked in our guide to the Agentforce agents retail businesses should prioritize in2026.
• Custom AI agents on Slack grew 300% since January,which is why the Experience Layer and the Slackbot MCP client both targetedSlack first.
The pattern isconsistent. Agents are moving from answering questions to completing workacross systems, and that shift is exactly what a headless architecturesupports. When an agent needs to read a case, apply a business rule and issue arefund, the constraint is rarely intelligence. It is access.
Searchinterest here runs high, so it is worth being precise about which tools dowhat. Salesforce lists the following as supported surfaces and clients.
• Coding agents: Claude Code, Cursor, Codex andWindsurf connect through native MCP servers, APIs, skills and CLI commands.Agentforce Vibes 2.0 covers the same ground natively inside Salesforce.
• Assistant and chat surfaces: ChatGPT, Claude,Gemini, Perplexity, Slack, Microsoft Teams, WhatsApp and Notion can act as deliverysurfaces through the Experience Layer or MCP apps.
• Model providers: The AI Trust Layer supportsOpenAI, Anthropic, Gemini, Meta Llama, Mistral, open source models and AmazonBedrock.
• Data and integration: Data 360, MuleSoft integration, Informatica, zero copyfederation and a governed data foundation supply the contextagents reason over.
One caution.The tool list is long, and the temptation is to connect everything in week one.Pick the clients your security team can audit and log, and add the rest onceyou have observability running.
Most failedagent programs fail for the same reason. They start with the technology insteadof a workflow that hurts. Here is the order that works.
1. Pick one workflow with volume and clear rules.Case triage, order status, lead qualification, document verification. You wantrepetition, defined success criteria and a measurable baseline before you toucha tool. Lead qualification is often the cleanest first candidate — see how an autonomous lead pipeline was built for Euclidon Agentforce.
2. Fix context before capability. An agentconnected to a raw database does not know the customer has an open escalation,a renewal in 30 days and a breached SLA. That context lives in your CRM anddata layer. Clean it first, or the agent will reason confidently from badinputs. Grasp Technologies took exactly this route, unifying fragmented data before layering agents on top.
3. Move enforcement into the platform. Once the UIstops being the entry point, UI level guardrails stop protecting you.Validation rules, the sharing model, formula fields and Apex have to carry theload for human and agent callers alike.
4. Expose a small, idempotent tool set. An agentdecides execution order at runtime, so you cannot rely on sequence to protectdata integrity. Every tool you expose must be safe to call twice. Start withfive tools, not fifty — and note that Salesforce made the same callarchitecturally with its four-tool MCP server design.
5. Define what good looks like before launch. Writethe behaviour rules in Agent Script, run Testing Center against edge cases, andset Custom Scoring Evals that reflect your policy. Scoring an agent on whetherit declined an out-of-policy request correctly beats scoring it on whether itresponded.
6. Instrument, then widen. Turn on observabilityand session tracing from day one. Run A/B tests before promoting a version.Only then extend to the second workflow — in a manufacturing estate that secondstep is usually field service and dealer communication.
A realisticfirst outcome for a mid-sized US business is one production workflow liveinside a quarter, with the governance pattern reusable for everything thatfollows. Teams that try to launch eight agents at once usually ship none. Our Agentforcecase studies show what that first quarter tends to produce acrossdifferent industries.
Theory helpsless than a working deployment. Broughton Partners operates in legal servicesand tech-enabled compliance, bridging law firms and claimants. Their fulfilmentteam was manually processing more than 20 binary and discernment checks percase, and those audits happened too late in the intake cycle. The result was predictable:processing bottlenecks, compliance errors and claimants disengaging beforepackets reached litigators.
The build used18 individual autonomous Agentforce agents running under a centralisedorchestration layer, integrated through MuleSoft and Sales Cloud with customand open APIs. Three design choices carried the outcome.
• Multimodal document verification agents checked recordsagainst document data using custom prompt templates.
• An extensible API integration layer verified recordsagainst proprietary and government databases through MuleSoft.
• Localised validation agents handled complexcross-object checks inside Salesforce.
The teamapplied AI where discernment was genuinely needed and deterministic logic whereexecution had to be reliable. That split kept total cost of ownership sensibleand kept the system stable, which matters more than it sounds when aprobabilistic caller sits in front of a compliance process.
Results: 16xfaster case processing, a 10% reduction in case drop-off, and an initial 5% ofcases routed end-to-end with no human intervention. Read the full write-up: 18 Agents, 0 Bottlenecks: Scaling Audits for BroughtonPartners with Intelligent AI Orchestration.
• Treating headless as a migration. It extends theplatform. Your Lightning apps and admin workflows can stay exactly where theyare.
• Exposing the whole org on day one. Every toolyou publish is a surface an agent can call. Scope tightly, expand deliberately.
• Ignoring idempotency. Non deterministic callersretry, reorder and repeat. Design for that or expect duplicate records.
• Leaving governance in the interface. If a ruleonly exists as a required field on a page layout, an agent will route straightaround it.
• Measuring conversations instead of completed work.Salesforce tracks an Agentic Work Unit, which is one discrete task an agentactually finishes. That is the metric your executives care about, not messagevolume.
A shorthonesty check. Headless earns its cost when several of these are true.
• You want agents to complete multi step work, not justanswer questions.
• Your users live in Slack, Teams or WhatsApp more thanin a Salesforce tab — common in high-volume business services operations whereclient interaction volume outpaces headcount.
• You have a customer facing experience where brandcontrol matters and Experience Cloud templates constrain you.
• Your developers already work in Cursor, Claude Code ora similar environment.
• You run agents from more than one vendor and lack asingle governance view.
If none ofthose apply, the classic model is still the cheaper answer. Good architectureadvice sometimes means waiting a release cycle.
What is Salesforce Headless 360 insimple terms?
It is a way touse Salesforce without the Salesforce screen. Every major capability isavailable as an API, an MCP tool, or a CLI command, so a developer, a script oran AI agent can read data, run workflows and complete tasks from anywhere.Salesforce announced it at TDX on April 15, 2026 and expanded it significantlyon August 19, 2026.
Does Headless 360 replace LightningExperience or Experience Cloud?
No. Lightningcomponents and browser experiences continue as they are. Headless 360 addsarchitectural flexibility so you can reach the same platform through a browser,a voice channel, a Slack agent or a custom React app. Most organizations runboth models side by side.
Do I need Agentforce to useSalesforce Headless 360?
Not for everyuse case. You can connect a coding agent to your org through MCP tools and APIswithout building an Agentforce agent. Agentforce becomes necessary when you want tobuild, deploy and govern autonomous agents inside the platform, with lifecyclecontrols like Agent Script, Testing Center and observability attached.
How long does a first headlessAgentforce deployment take?
It depends ondata readiness far more than on build effort. Salesforce customer Enginereported production ready agents in 12 days. SaasWorx typically gets a first USclient agent live in around five weeks, including discovery, data connection,governance setup and testing. Workflows with clean data and defined rules landat the fast end of that range.
How does Headless 360 handlesecurity and compliance?
Agents inheritthe controls you already approved. Identity, permissions, field level security,sharing rules, approval chains and compliance policies travel with the platformregardless of the entry point. The change you must make is moving any rule thatlived in the UI down into schema level enforcement, since the UI is no longerthe only door.
Is Salesforce Headless 360 generallyavailable?
Partly. Thecore package and hosted MCP servers went GA in April 2026, Slackbot’s MCPclient in June, and the Data 360 MCP Server in August. The Headless 360 MCPServer entered beta in July and some toolsets remain in Beta or DeveloperPreview. Check the Salesforce CLI release notes for current status beforecommitting to a delivery date.
Headless 360answers a structural problem rather than a cosmetic one. Software built forhumans clicking through screens cannot be operated by agents, and agents arenow doing a growing share of enterprise work. Salesforce responded by turningthe platform into an execution layer that either kind of user can reach, whilekeeping the context, workflows and trust controls that took years to build.
The technologyis largely available today, with some pieces still in beta. The harder worksits in data quality, governance design and choosing the first workflow well.That is where most programs succeed or stall.
SaasWorx workswith US organizations on exactly that sequence, from Agentforce use case selectionthrough data integration, agent design, testing and production support. If youwant a second opinion on where headless fits your roadmap, booka consultation with our team and we will walk through your workflowsand give you a straight answer, including when the answer is not yet.
.png)
