Agentforce Builder Considerations

Carefully review the current considerations and limitations for the new Agentforce Builder.

Required Editions

Available in: Lightning Experience

Available in: Enterprise, Performance, Unlimited, and Developer Editions. Required add-on licenses vary by agent type.

Agent actions trigger billing when they run, whether they run deterministically (for example, in reasoning instructions) or during agent reasoning with an LLM. Utilities such as escalations to a representative, setting variables, or transitions to another subagent don't incur billing as agent actions.
You can’t modify agents that you created in the legacy Agentforce Builder in the new builder. Instead, upgrade your agent from the legacy builder to the new builder.
Agents created in both the new Agentforce Builder and the legacy builder are available in the Agents list in Agentforce Studio and in the Agentforce Agents Setup page list view. Clicking the agent name opens it in the compatible builder. In the Setup page list view and the legacy builder, only committed versions of agents created in the new builder are visible.
For agents created before the week of August 3, 2026, a single agent version can have different numbering between the legacy and new builders because of metadata differences. In the legacy builder, draft versions can appear to be skipped. For example, you have two versions of an agent in the new builder. Version 1 is committed and Version 2 is a draft. In the Agentforce Agents Setup page list view, only Version 1 is visible. In the new builder, you create and commit a new version. In the new builder, the new version appears as Version 3. In the legacy builder, the draft version is skipped, so the new version appears as Version 2.
Some features are only available in Script view. For details about these features and Agent Script, see Agent Script.
- Customizing an agent action's input or output with a custom Lightning type isn't supported in Canvas view. As a workaround, create a custom action from the asset library, edit the Input Rendering or Output Rendering parameter, and then add the action to a subagent in Agentforce Builder.
- You can't select a search provider for the Search the Web agent action in Canvas view. As a workaround, add an action input that stores the provider name.
Editing the fields of an agent action in Canvas view can cause validation issues. A fix is on the way. In the meantime, modify any fields or parameters for your actionin the action definition in the associated Subagent block in Script View. If you prefer a form-based fix, you can create or edit an action in the asset library and add the action to your agent.
When Agent Script can't compile, the Canvas view underlines the code that produces the error in red. Switch to Script view for more details and to fix the error. It's possible to make invalid changes in the Script view that make the Canvas view unavailable. To switch back to the Canvas view, fix the errors in the Script view.
When previewing custom Lightning types (CLTs) in Agentforce Builder, these considerations apply.
- Preview for CLTs is supported for Agentforce Employee agents and Agentforce Service agents. Service agents must have an Enhanced Chat v2 connection, and you must select the Enhanced Chat v2 connection from the Preview Mode dropdown in the Agentforce Builder Preview panel.
- To preview CLTs for an agent, start a preview conversation in live test mode.
- Agents can be in draft or committed states.
When you use the render nested inline action in an agent action, these considerations apply.
- The render nested inline action tells the agent to send the agent action's full output. For example, if a user asks for two places to visit and the agent calls an agent action that returns a list of ten places to visit, the render nested inline action tells the agent to show the list of ten places. To customize what's shown, edit the agent action's inputs or the subagent's Actions Available For Reasoning section.
- Currently, you can't add the render nested inline action to an MCP tool action.
- Currently, the render nested inline action isn't supported with multi-agent orchestration.
Starting in May 2026, Salesforce adds wss://*.livekit.cloud and https://*.livekit.cloud to your Trusted URLs when you create an agent or when you open an existing agent in Agentforce Builder. These URLs are added so that you can preview and deploy voice agents.
When you create an agent from a template or add a standard subagent or action to your agent, the agent metadata, subagents, and actions are copied to your agent. To protect your deployed agents and customizations, changes made to standard assets in the asset library aren't automatically applied to the agents that use them. To get changes to an agent template, create a new agent from the template and recreate any customizations. To get changes to a standard subagent or action, add the subagent or action to your agent from the asset library and recreate any customizations.