Agentforce changes in the Winter '26 release

If you've been using agent versioning for downtime-free deployments, you'll have noticed that while your GenAiPlannerBundle cloned automatically, you had to manually clone any referenced topics and actions. This meant changes to a new agent version often affected previous versions too.

Winter '26 restructures Agentforce metadata so agent versions are now fully isolated from each other. But this means some components won't be where you expect to find them.

In Summer '25, bot versions and planner bundles were versioned together, but topics and actions were shared between versions. You had to manually duplicate them and update references in your planner bundles. Any changes to a topic or action could change behavior across multiple agent versions.

When you added a standard (out-of-the-box) topic or action to your agent, Salesforce inlined a copy into your GenAiPlannerBundle. If you looked for that topic under GenAiPlugin metadata, you wouldn't find it - you needed to check inside the GenAiPlannerBundle.

Winter '26 introduces a more structured layout with global topics and actions, and local topics and actions.

You can now create GenAiPlugins and GenAiFunctions directly in the Agent Asset Library. These are global topics and actions that you can add to any agent within Agent Builder. Create topics or actions here if you want to reuse them across multiple agents.

When you add a topic or action to an agent in Agent Builder, it's copied into the GenAiPlannerBundle as a local topic or action with a reference back to the original global asset. You can now customize the topic or action safely, without affecting other agents.

If you create a new topic or action within Agent Builder, it's only created as a local asset. You won't find it in Asset Library, which means you won't see it in a Gearset comparison, Workbench, or the Salesforce CLI as a GenAiPlugin or GenAiFunction.

This isolation means changes to agent versions are now truly separate. Updating one version won't introduce side effects into any others. Customers can now adopt agent versioning and avoid deactivating agents during deployments, which reduces downtime.

Here are some common deployment errors and what they mean:

The process for deleting agents has changed. You could delete v64 agents in the same package as their dependencies (like Flows or Apex). But with new-style agents, you need to remove local topics and local actions first before you can delete the agent itself.