[object Object]

The Pitch

TDX 2026 (Moscone West, April 15–16) framed the platform as an agentic-era runtime. Headless 360 makes Salesforce a capability layer that renders across Slack, voice, WhatsApp, not just a destination UI. Concretely, every Sales Cloud, Service Cloud, and Data 360 capability that previously lived behind a Lightning page is now exposed as an MCP tool with structured I/O contracts, an OpenAPI spec, and a governance binding to the Trust Layer. The keynote demoed a customer ordering a product through WhatsApp, the same flow handled by a voice IVR, and the same flow embedded in a custom React-Native mobile app — all backed by one server-side capability definition. The selling point isn’t novelty; it’s that you write the logic once and consume it from any surface a customer reaches you on.

Agent Fabric

A trusted control plane for multi-vendor AI. Expanded agent and MCP discovery, deterministic orchestration primitives, LLM governance. Salesforce’s answer to agents from different vendors needing to coordinate. The core abstraction is the Topic — a deterministic state machine wrapping LLM calls. Topics declare their inputs, outputs, and side effects up front; the runtime guarantees those contracts even when the underlying LLM hallucinates. Multi-vendor support means an Anthropic-built agent and a Microsoft Copilot agent can both register as Topic handlers, route through the same Trust Layer, write to the same audit log, and respect the same sharing rules. The Agent Fabric registry is browsable in Setup > Agent Fabric > Registered Agents, with policy bindings (rate limits, allowed objects, masking rules) per agent.

Agentforce Vibes 2.0

Developer assistant with multi-model support — Claude Sonnet 4.5 default, switchable to GPT-5 or Salesforce’s own models. Understands your org’s schema and code patterns, not just generic boilerplate. The schema awareness is the differentiator: a prompt like “write a trigger that prevents Account deletion when active Opportunities exist” produces:

trigger PreventAccountDelete on Account (before delete) {
    Set<Id> accountIds = Trigger.oldMap.keySet();
    Map<Id, Integer> activeOppCount = new Map<Id, Integer>();
    for (AggregateResult ar : [
        SELECT AccountId, COUNT(Id) cnt
        FROM Opportunity
        WHERE AccountId IN :accountIds AND IsClosed = false
        GROUP BY AccountId
    ]) {
        activeOppCount.put((Id) ar.get('AccountId'), (Integer) ar.get('cnt'));
    }
    for (Account a : Trigger.old) {
        if (activeOppCount.get(a.Id) > 0) {
            a.addError('Cannot delete account with active opportunities');
        }
    }
}

The trigger uses your actual API names and respects your org’s bulkification conventions because Vibes scanned existing classes during setup.

Salesforce Multi-framework

Build native Salesforce apps starting in React with platform-grade auth, security, governance. Signals Salesforce accepting the reality that developers want framework choice, not LWC-or-nothing. The React runtime ships as Lightning Web Runtime (LWR) extensions; component lifecycle hooks bridge React’s useEffect to LWR’s connection callbacks. Authentication, FLS enforcement, and governor limits apply identically to React and LWC code paths. The compiler outputs the same compiled bundle structure, so deployment, debugging, and source tracking work through the existing sf CLI without separate tooling.

What Changed in 2026

Pre-TDX, Salesforce’s developer story was “learn LWC, deploy through DX, run on Lightning.” Post-TDX, it’s “pick your framework, expose your capabilities through MCP, render anywhere a customer touches.” The shift is comparable in scope to the Aura-to-LWC transition of 2018 — except this time it’s additive rather than replacement.

Common Failure Modes

Treating Headless 360 as production-ready. Most components were Pilot or Beta at announcement. Production migrations should wait for Winter ‘26 GA confirmations. Agent Fabric without per-Topic rate limits will burn Agentforce credits unpredictably when third-party agents register. Set caps in Setup > Agent Fabric > Quotas before opening registration to non-Salesforce agents.

What to do this week

Watch the TDX 2026 Headless 360 deep-dive on Salesforce+. Identify one capability your team currently exposes as a Lightning component but should also expose as an MCP tool. Sketch the contract; the implementation plan follows from there.

[object Object]
Share