blog
2026-09-19Winter '271 min read

Salesforce Winter '27 Agentforce deployments

Use API 68.0 Agentforce metadata when both orgs are on 68.0; retain API 67.0 and assemble dependencies manually for Summer '26 production.

Abstract artwork for the article "Salesforce Winter '27 Agentforce deployments"

Salesforce Winter '27 introduces AiAgentDefinition and AiAgentDefinitionVersion for Agentforce agents from API 68.0. Salesforce CLI automatically retrieves an agent with its dependent Apex classes, flows, and prompt templates. See Salesforce’s agent metadata release note.

Choose Agentforce metadata for API 67.0 or 68.0

Use the new metadata types only when both orgs are on API 68.0. While production remains on Summer '26, pin the manifest to API 67.0.

Source–target conditionManifest API versionAgent metadata types
Both orgs are on API 68.068.0AiAgentDefinition, AiAgentDefinitionVersion
Production remains on Summer '2667.0AiAuthoringBundle, Bot, BotVersion

On the API 67.0 path, assemble related components manually at the intended agent version. Compare the assembled deployment against the agent’s related Apex classes, flows, and prompt templates; add missing components before deployment.

Tell the release owner whether the move can use automatic dependency retrieval or requires manual component assembly. While production remains on Summer '26, include that manual work in the release plan.

release items covered