Dreamforce 2026 Announcements: Claudeforce Was the Opening Move

What Salesforce Announced at Dreamforce ’26, and What It Actually Changes

Three weeks ago we published a post arguing that Claudeforce was not really a product announcement. It was Salesforce putting a brand name on an architecture that already existed, and the interesting question was whether the company would commit to it.

Dreamforce ’26 answered that question. Salesforce committed.

Over three days in San Francisco, Marc Benioff and Patrick Stokes laid out a version of Salesforce where the user interface is no longer the front door. Claudeforce turned out to be one piece of a much larger bet called AIforce. If you run a Salesforce org, this is the most consequential set of Dreamforce 2026 announcements in years, and most of the coverage is burying the parts that matter to you.

We Said Claudeforce Was a Pattern, Not a Product. Dreamforce Confirmed It.

In our August post on Claudeforce, we made a specific claim: the plugin was the visible tip of something structural, and teams should prepare for a world where work happens outside the Salesforce UI.

Salesforce spent the Dreamforce main keynote saying exactly that, out loud, with a product line behind it. Patrick Stokes put it plainly:

The numbers behind the claim are real. Salesforce reported 30,000 customers now live on Agentforce, and 7 billion agentic work units delivered across Agentforce and Slack, with 3.2 billion of those in Q2 alone. Fulton Bank told the Dreamforce audience it has saved 80,000 hours, attributed $389 million in loans and deposits to the technology, and cut complaint resolution times by four days.

This is no longer a demo. It is a deployment category.

AIforce Is the Real Dreamforce 2026 Announcement

AIforce is the umbrella. The thesis is that people should not have to come to Salesforce to get work done, so Salesforce comes to them. It has four parts:

The critical detail, and the one Salesforce deserves credit for getting right: every action still runs inside your existing permissions and business rules. Benioff was direct about the data question. “Your data is your data. It does not go in the models.” Zero data retention with the model provider.

That matters because the objection we hear most often from CIOs is not “can it work.” It is “who is accountable when it does something wrong.” Running through the existing permission model is the right answer to that question.

Named Agents Lower the Floor. Scoping Still Sets the Ceiling.

Salesforce introduced seven job-ready agents, each built for a specific role and configurable by the business rather than IT:

This is a genuinely good move by Salesforce. Starting from a named role beats starting from a blank builder, and it collapses weeks of early design work.

Here is the part to plan for. A role label is not a job definition. Hiring Casey takes an afternoon. Deciding what Casey is allowed to refund without approval, which accounts it must never touch, what “resolved” means for your business, and when it hands off to a human is the actual project. The work did not disappear. It moved from building the agent to governing it.

The Most Useful Announcements Were the Least Glamorous

With 30,000 customers live, Salesforce now has a large population of agents running in production, and some of them are underperforming. The tooling built for that problem was the quiet highlight of the week:

• Agent Optimizer. Traces problems in production agents, suggests configuration changes, and generates test cases so fixes are verifiable.
• Agentforce Observability. Session logs, response quality scoring, action traces, and latency metrics, including monitoring for live voice interactions.
• Long-Horizon Runtime. The architecture that lets an agent pursue a goal across weeks. Goal definition, planning, human checkpoints, signal processing, continuous refinement. Salesforce deliberately kept humans in the loop rather than chasing full autonomy, which is the correct call.
• Builder Central. A free AI-assisted app and agent builder with governance controls included, reading your org metadata and Data 360 context, with one-click sandbox deployment. Beta opens the week of September 21.

If you already have agents running, this cluster is worth more to you this quarter than anything else announced.

Salesforce Just Acknowledged You Will Run Agents From Multiple Vendors

The strategic signal of the week came from the governance announcements.

• Salesforce Guardian. A security layer providing agent identity, risk discovery, and data classification.
• Agent Fabric. A central registry that manages agents across Azure, AWS, Google, and Agentforce, with visibility into lineage, skills, errors, and cost.
• Trusted Enterprise AI Harness. A six pillar framework covering context, agency, action, governance, security, and models, with an AI control plane for multi-vendor environments. In preview now, broadly available in early 2027.

Read Agent Fabric carefully. Salesforce is not pretending every agent in your enterprise will be an Agentforce agent. It is offering to govern the ones that are not. That is a mature, customer-aligned position, and it matches what we see in every org we work in.

Alongside governance came Koa, Salesforce’s first CRM reasoning model, built on NVIDIA Nemotron and post-trained on a synthetic dataset modeled on nearly three decades of CRM deployments. Salesforce reports it matches or beats leading models on CRM actions with three times fewer errors on its own benchmark. Koa is in pilot with customers including Formula 1, UChicago Medicine, and Xero, with general availability expected winter 2026 in US regions.

Domain-tuned models beating general-purpose models on domain tasks is the expected result, and a welcome one. Just validate it against your own cases rather than the vendor benchmark, the same way you would with any model.

What to Do in the Next 90 Days

Frequently Asked Questions

What was the biggest announcement at Dreamforce 2026?

AIforce. It brings Salesforce data and actions into the interfaces people already use, including Claude, Slack, Teams, and Lightning, rather than requiring them to work inside the Salesforce UI. Its four components are Claudeforce, Slackforce, Agentforce Coworker, and the Headless Toolkit.

Is Claudeforce available now?

Yes. Claudeforce moved to open beta at Dreamforce ’26. You request access through AppExchange and provide your org ID, and it activates immediately. It ships with 37 prebuilt sales skills and operates with zero data retention at the model provider.

When will Koa be generally available?

Salesforce expects general availability in winter 2026, initially in US regions. A pilot program running in October targets enterprises with more than 1,000 active seats. Salesforce has not disclosed pricing.

Do I need to replace my existing Agentforce agents?

No. The named agents and the new tooling are additive. The more valuable move for most orgs is to instrument and optimize the agents already in production before deploying new ones.

We Have Been Building This All Along

Cirrius Solutions sits on both sides of this announcement. We have implemented Salesforce for more than fifteen years, we are an Anthropic partner, and we run our own operations on Claude agents connected to our own Salesforce org. We were building on MCP and headless patterns before they had a keynote name, which means we already know where this architecture is genuinely excellent and where it needs careful design.

Salesforce built the platform. The advantage goes to the teams that scope it well.

If you want a clear read on what these Dreamforce 2026 announcements mean for your specific org, let’s talk.