← back to the release
new featureAgentforce Development
Move Agents Between Orgs More Easily with Simplified Agent Metadata Types
From API version 68.0, Agentforce agents are represented by two metadata types, AiAgentDefinition and AiAgentDefinitionVersion, and Salesforce CLI retrieves an agent with all its dependent Apex classes, flows, and prompt templates automatically. Previously a sandbox-to-production move needed at least three metadata types and manual assembly of every related component at the right agent version. Both orgs must be on API 68.0 to use the new types; while production is still on Summer '26, keep using AiAuthoringBundle, Bot, and BotVersion by pinning API 67.0 in the manifest.
identifiers
AiAgentDefinitionAiAgentDefinitionVersionAiAuthoringBundleBotBotVersionsf project retrieve start
metadata types
AiAgentDefinitionAiAgentDefinitionVersionAiAuthoringBundleBotBotVersion
api versions
68.067.0
flags
enabled by defaultno action requiredmin api 68
- how
- Update Salesforce CLI, reference AiAgentDefinition and AiAgentDefinitionVersion in the manifest, and run 'sf project retrieve start --metadata AiAgentDefinitionVersion --root-type-with-dependencies AiAgentDefinitionVersion'. Both source and target orgs must be on API 68.0.
- who
- Developers and admins who deploy Agentforce agents between orgs.
- when
- Rolling out with Winter '27, starting with preview sandboxes the week of August 24, 2026.
- where
- Enterprise, Performance, Unlimited, and Developer editions with Foundations or Agentforce 1.