Claudeforce versus Agentforce, in plain terms

If your org already uses Agentforce, the Claudeforce announcement can read like something entirely new arrived. Some of it is. Some of it formalizes what was already quietly true.

---

What was already true before the announcement

Claude has been available as a model option inside Agentforce since late 2025. If your org had already selected Claude as the reasoning model behind an Agentforce agent, the core capability, Claude reasoning over your CRM data inside a Salesforce-governed workflow, isn’t new. It’s the same underlying relationship the announcement is now naming and expanding.

---

What’s actually new

The direction reverses, not just extends. Agentforce brings agent capability into Salesforce. Salesforce in Claude brings Salesforce into Claude, as a plugin you use from Claude’s own interface, reasoning over live CRM data without opening a Salesforce screen at all. That’s a genuinely different surface, not a bigger version of the same one.

One connection instead of many. Before, an org that wanted several Agentforce agents connected to different systems typically built or configured each connection somewhat separately. The single-admin-connection model, one MCP connection centrally managed and scoped to each user’s existing permissions, is a real administrative change, described directly in coverage of the launch as “the real innovation,” ahead of anything about the underlying model.

Default model status, not just availability. Claude is now the default model for Agentforce Vibes and Agentforce Coworker specifically, not merely one option among several. Agent Builder still lets you choose a different model. Where Claude is the default, that’s a deliberate platform decision, not just Claude being newly present.

Named, structured skills instead of general capability. The 37 prebuilt sales skills in Salesforce in Claude are described as co-engineered between the two companies, encoding specific field logic and pipeline definitions, rather than a general-purpose agent you’d have to configure and prompt yourself. That’s a narrower, more opinionated product than “Claude, with access to your org.”

---

Side by side

	Agentforce (before Claudeforce)	Claudeforce
Primary interface	Salesforce	Either: Salesforce, or Claude itself
Claude’s role	One selectable model among several	Default for Vibes and Coworker; still selectable elsewhere
Connection setup	Per-agent or per-integration configuration	One admin-managed connection, scoped per user
Skills	Built and configured per use case	37 prebuilt, named skills ship with the plugin
Direction	Brings agent capability into Salesforce	Also brings Salesforce into Claude

Neither column replaces the other. Salesforce’s own framing, that they complement rather than compete, matches what’s actually shipping: a Salesforce-first workflow still runs through Agentforce; a Claude-first workflow runs through the plugin. The CRM data underneath is the same in both directions.

---

When it breaks

Assuming this replaces an existing Agentforce setup. It doesn’t. An agent you’ve already built in Agentforce keeps working exactly as it did. Claudeforce adds a second way in, it doesn’t retire the first one.

Treating “Claude is the default” as “Claude is required.” Agent Builder retains model choice. Default means what your org gets without changing anything, not a restriction on what you’re allowed to configure.

Expecting the 37 skills to be available inside Agentforce itself. They’re specifically part of Salesforce in Claude, the plugin used from Claude’s interface. An Agentforce agent built inside Salesforce doesn’t automatically inherit them; they’re a different surface with its own capability set.

---

What to try next

If you’re deciding whether a pilot is worth the setup described in the admin checklist, the honest framing is that you’re not evaluating whether Claude works with Salesforce, that’s already established. You’re evaluating whether the specific new surface, Claude-first access to your CRM with one centrally governed connection, is worth adding alongside what you already have.