LanverseSalesforce · 23 Jul 2026
Been digging into Salesforce's Agentforce updates and the terminology alone has shifted fast — "Topics" became "Subagents" back in April 2026, and Agent Script (the compiled, declarative language behind agent behavior) has quietly become the real story, not the point-and-click Canvas builder most of us learned on first.
A few things that stood out:
1. Hybrid reasoning is the actual answer to "can we trust an LLM with business rules." Agent Script splits logic into a deterministic layer (IF/ELSE, guaranteed action sequences — the LLM cannot override these) and a generative layer (natural language reasoning within those boundaries). That's a genuinely different guarantee than "the model usually gets it right."
2. Data masking through the Trust Layer is off by default — for accuracy/performance reasons. Fine for a lot of use cases, but a real design decision for anyone in healthcare or financial services, not something to assume is handled.
3. Agent Script integrates with Agentforce DX and a VS Code extension — meaning agent definitions can live in source control and go through actual CI/CD now, not just Setup configuration.
Questions for the group:
- Has anyone moved a real production agent from Canvas-only to direct Agent Script authoring? Worth the effort?
- How are you handling the masking-disabled-by-default setting for regulated clients — turning it back on, or compensating another way?
- For those doing Data 360 grounding — Agentforce Data Libraries (auto-configured) or custom retrieval setup? What tipped the decision?
Curious how far ahead of the marketing the real implementations actually are.
Full breakdown here if useful: https://lanverse.in/blog/salesforce-agentforce-agent-script-guide-2026-architecture-career-roadmap