The Summer ’26 release notes are out, preview orgs are live, and sandbox upgrades start May 8. If you only have an hour to look at this release, here’s where to spend it.

The headline isn’t subtle: this release is about Agentforce going from “interesting” to “operationally serious.” There’s also useful work in Flow, Service Cloud, and the developer toolchain, but the AI side is where most of the new surface area lives.

Summer ’26 — Themes at a GlanceAgentforce DXMCP ServerVibe IDEAgent Builder APIReliabilityPrompt versioningTesting FrameworkCustom Apex actionsService ImpactAgentic MilestonesVoice Visit LoggingField Service agentsSandbox upgrade begins: May 8, 2026

The big Agentforce shifts

Three changes stand out for anyone running Agentforce in production.

• Prompt versioning. Finally. You can now track, compare, and roll back prompt changes. If you’ve ever made a prompt edit and watched agent behavior change in confusing ways, this is the safety net you’ve been missing.
• Agent Testing Framework. A way to validate agent behavior with reproducible test conversations. Pair this with prompt versioning and you finally have something resembling a real release process for agents.
• Custom Agent Actions in Apex. Full data model access from inside an agent. The previous limits on what an action could touch were the most common reason teams hit a wall. This opens it up.

Dynamic grounding goes three levels deep

Prompts can now reference related records up to three levels deep. In practice, that means an agent answering a Case question can pull in the Account, the Contact, and the related Opportunities without you writing a flow to assemble that context. For service use cases especially, this turns mediocre agents into useful ones.

Service Cloud: Agentic Milestones

Agentic Milestones let Agentforce automatically handle SLA-related communications: drafting and sending the initial response, sending periodic status updates, and escalating before milestones breach. For high-volume service orgs, this is the kind of feature that actually changes capacity.

Worth noting: this is going to change how you measure agent performance. “Time to first response” gets gamed instantly when the response is automated. Plan your KPIs around resolution, not response.

For developers

Agentforce DX MCP Server and the Agentforce Vibe IDE move agent development out of clicks and into a real developer workflow. If you’ve been waiting to commit agents to source control, this is the release that makes it sane.

How to prep

1. Spin up a preview sandbox the week of May 8 if you haven’t already. Get hands on the Agentforce changes specifically.
2. Build an eval set for any agent you have in production. Run it pre-upgrade, run it post-upgrade, compare outputs.
3. Audit your milestones if you’re a Service Cloud customer. Decide which ones become agentic and which stay human-driven.
4. Check your prompts for any that depend on undocumented behavior — those are the ones most likely to shift.

The bottom line

Summer ’26 is the release that takes Agentforce from “we’re experimenting” to “we can operate this in production with the same rigor as the rest of our platform.” The features that make that real — prompt versioning, testing framework, dynamic grounding, custom actions — are the ones to focus your evaluation on. Everything else can wait until you’ve validated those work for you.