Why Salesforce Rebuilt the Agent Builder
The legacy Agentforce Builder proved that low-code agent creation worked — but enterprise customers hit a familiar wall: behaviour that was entirely interpreted by an LLM is hard to predict, hard to test and hard to govern. Impressive demos stalled before production.
Salesforce's answer, rolled out through the Agentforce 360 releases following Dreamforce 2025, is a ground-up rebuild of the builder around three beliefs: models alone are not enough, files are where humans and AI build together, and enterprises need full control over agent reasoning. The result is the new Agentforce Builder — the hub we refer to as Builder Central for agent design — with hybrid reasoning, Agent Script and an embedded AI assistant.
The strategic point: agents are becoming software artifacts. Like Apex classes or flows, they now have a source representation you can read, diff, version and review — which is what makes them governable at enterprise scale.
Core Features of the New Agentforce Builder
Six capabilities define the new building experience and why it matters for production agents.
Hybrid, graph-based reasoning
The new builder runs on an upgraded, graph-based Atlas Reasoning Engine. Instead of leaving every decision to LLM interpretation, you can define a structured, predictable path for the parts of the conversation that must be deterministic — and keep free-form reasoning where flexibility helps.
Agent Script
Agent Script is the new language for building agents. It combines natural-language instructions with programmatic expressions, so business rules, transitions and conditions can be written as inspectable, versionable code rather than buried in a prompt.
Canvas and Script views
Build conversationally in the Canvas view, then toggle to the Script view for syntax highlighting and real-time validation. The two views stay in sync, so admins and developers can work on the same agent at their own altitude.
Built-in AI assistance
Agentforce is embedded in the builder itself. Describe the agent you want in plain language and the assistant converts it into topics, actions and instructions you can review, adjust and test.
Trust Layer and platform integration
Agents remain protected by the Einstein Trust Layer and stay wired into the Salesforce Platform — Flow, Prompt Builder, Apex, Data 360 and your existing permissions and sharing model.
Test and preview before release
The graph-based engine lets you preview defined flows and conversational paths, making agent behaviour observable and testable before customers or employees ever touch it.
Agentforce Builder vs Agentforce Vibes
The two tools overlap — both can create agents — but they sit at different layers of the development lifecycle.
A simple rule of thumb: use Vibes to move faster as a developer — generating code, tests, apps and agent scaffolding in your IDE. Use Builder to design, preview and govern how a production agent actually reasons and acts. In a mature workflow, Vibes accelerates the build; Builder is where behaviour is signed off.
Release Details and Availability
The new Agentforce Builder was unveiled at Dreamforce 2025 as part of the Agentforce 360 launch and has been rolling out through subsequent releases, with Salesforce publishing Trailhead modules and admin guidance as capabilities reach general availability. Agentforce Vibes 2.0 reached general availability as the redesigned agentic development environment, with point releases continuing to add capabilities such as Plan Mode grounding and new skills.
A practical caveat: feature availability, edition requirements and pricing for Agentforce, Agent Script and the Vibes IDE continue to evolve. Some capabilities arrive in preview before GA. Confirm the current release status and licensing for your org with Salesforce's release notes and your account team before planning a rollout.
KVP View: Recommendations for the Developer Community
Learn Agent Script early. It is becoming the durable artifact of agent design — the thing that gets reviewed, versioned and audited. Developers who can read and write Agent Script will own the most consequential part of agent delivery, the same way Apex skills defined the last decade of Salesforce development.
Design deterministically where money, compliance or customers are involved. Hybrid reasoning is the headline feature for a reason. Use defined paths for anything with financial, regulatory or reputational impact, and reserve open-ended reasoning for discovery and conversation.
Pair Vibes with Code Analyzer and real review. AI-generated code that passes your standards gates is a productivity win; AI-generated code merged without review is tomorrow's technical debt. Keep the human approval step sacred.
Treat prompts, topics and actions as governed configuration. Changes to agent behaviour deserve the same change control as code: versioned, tested in sandboxes, and released deliberately.
How KVP Plans to Work with Agentforce Builder
At a high level, our delivery approach is evolving with the tooling. We plan to design agent behaviour in the new Builder from day one — using the Canvas view for collaborative design sessions with business stakeholders, and Agent Script as the reviewed source of truth for every agent we ship.
Our developers will use Agentforce Vibes to accelerate scaffolding, test generation and integration code, with our existing code review and quality gates unchanged. And we will continue to pair every agent build with the governance work we describe in our Guardian guidance — least-privilege running users, data classification, monitoring and human escalation — because the builder makes agents easier to create, not safer by default.
In short: faster building, same discipline. The new tooling compresses the build phase; it does not compress the design, testing and governance that make an agent production-worthy.
Five Steps to Get Started
Enable the foundations
Turn on Einstein and Agentforce in a Developer Edition or sandbox org, and open the new Agentforce Builder from Setup.
Build one agent conversationally
Describe a simple bounded agent to the embedded assistant and study the topics, actions and instructions it generates.
Toggle to Script view
Read the Agent Script behind your canvas design. Make one deliberate change in script and preview the effect.
Try Vibes on the same agent
Install the Agentforce Vibes extension or open the browser IDE and generate tests or an integration for your agent.
Add governance before sharing
Set the running user's least-privilege access, test denied paths, and define the human escalation route before anyone else uses it.
Official Salesforce Sources
Feature availability and packaging for Agentforce Builder, Agent Script and Agentforce Vibes continue to evolve; confirm current release status with Salesforce before planning a rollout.