We have built an Agentforce agent using AiAuthoringBundle metadata. However, while creating a second-generation managed package (2GP), we found that the .agent component cannot be included in the package.
Based on our understanding, the managed package can include the supporting components, such as Apex classes, Flows, custom metadata, permissions, and agent actions, while the Agentforce agent must be deployed, configured, activated, and published separately in the subscriber org after package installation.
Could you please clarify how other Salesforce ISV partners currently package and distribute Agentforce solutions?
Specifically, we would appreciate guidance on the recommended approach and detailed steps for:
Packaging the Agentforce solution’s supported components in a managed 2GP. Deploying the agent metadata to a subscriber org. Configuring package namespaces, actions, permissions, and other dependencies. Activating and publishing the agent after package installation. Automating or simplifying the post-installation setup process. Handling future agent upgrades and version changes. Following Salesforce’s recommended ISV and AppExchange distribution model for Agentforce solutions.
Please also confirm whether deploying the agent separately after installing the managed package is currently the recommended approach for ISV partners.
