Does Claudeforce Replace Agentforce? No. Here Is How They Fit Together

No, Claudeforce does not replace Agentforce. Claudeforce is the partnership between Salesforce and Anthropic, and its first product, Salesforce in Claude, lets employees work with Salesforce data inside Claude. Agentforce is Salesforce’s platform for AI agents that work autonomously or deal directly with customers. Claude actually runs inside Agentforce as a reasoning model, and Salesforce announced seven new Agentforce agents in September 2026. The two serve different kinds of work on the same data, permissions and business logic.

The confusion is understandable. Within three weeks, Salesforce launched Claudeforce, a new interface layer called AIforce and its own reasoning model, while also dropping “Agentforce” from several product names. This post explains what changed, what did not, and how the two fit together across the customer lifecycle. It then covers what this means for your roadmap.

Key takeaways

• Agentforce is for autonomous and customer-facing work. Salesforce in Claude is for employees doing their own work with Salesforce data in Claude.
• Claude runs inside Agentforce: it is a reasoning model for the Atlas Reasoning Engine, the default for Agentforce Coworker and Agentforce Vibes, and available in Agent Builder.
• Salesforce is still investing in Agentforce. Seven job-ready agents, a long-horizon runtime and multi-agent orchestration were all announced in September 2026.
• Three things did change: Salesforce’s own interface is now optional, Claude became the default model on the employee-facing side, and Salesforce added Koa, its own CRM reasoning model, for Agentforce.
• The “Agentforce” prefix was removed from some application names. The Agentforce agent platform was not.

Why people are asking

Four things happened close together:

1. August 26, 2026: Salesforce and Anthropic announced Claudeforce, with a plugin that brings Salesforce into Claude. Coverage focused on sellers no longer needing to open Salesforce at all.
2. September 15, 2026: Salesforce announced AIforce at Dreamforce, a layer that brings Salesforce to Claude, Slack and Lightning. It launched with three interfaces: Claudeforce, Slackforce and Agentforce Coworker.
3. The same week: Salesforce introduced Koa, its own CRM reasoning model, built on NVIDIA Nemotron.
4. Around Dreamforce: product names such as Agentforce Sales and Agentforce Marketing reverted to Sales Cloud and Marketing Cloud.

Put together, it looked as if Salesforce had quietly moved its AI strategy from its own agents to Anthropic’s assistant. The evidence says otherwise.

How we got here: a short timeline

Seeing the announcements in sequence makes the direction clearer. Salesforce has spent two years building out Agentforce. In 2026 it layered new ways to reach Salesforce on top of that work, rather than replacing it.

Read in order, the pattern is additive. Headless 360 and hosted MCP servers made Salesforce reachable from outside its own interface. Claudeforce and AIforce put that access to work in Claude and Slack. Throughout the same period, Agentforce kept getting new agents, a new runtime and new models.

What each one does

Five reasons Claudeforce does not replace Agentforce

1. Salesforce says they do different jobs

When Claudeforce launched, Patrick Stokes, Salesforce’s president of applications, said the two are not equivalent. He described Agentforce as built for autonomous work and work that touches the end customer, using Salesforce’s own help site agent as the example. He described Salesforce in Claude as a knowledge-worker agent for salespeople, designed to take the clicking and synthesis out of their day.

That split reflects a real difference in design. An Agentforce service agent must respond to a stranger at 2 a.m., follow policy and escalate to a human when needed, with nobody from your company watching each step. Salesforce in Claude assumes an employee is present, asks for approval before writing changes by default, and works on that employee’s own accounts and pipeline. For examples of the autonomous side in action, see our roundup of real-world Agentforce use cases working in 2026.

2. Claude runs inside Agentforce

Claudeforce is not only “Salesforce in Claude.” The Claudeforce announcement also covered “Claude inside Salesforce”:

• Claude is available in Agentforce as a reasoning model for the Atlas Reasoning Engine.
• Claude powers Agentforce Vibes and Agentforce Coworker by default.
• Claude is available in Agent Builder.

Salesforce also said Claude is the first model provider fully integrated within the Salesforce Trust Boundary, through Amazon Bedrock.

A partnership that makes Claude a default model inside Agentforce is a strong signal that Agentforce is staying. The partnership strengthens Agentforce’s reasoning while also opening a second front door for employees.

3. Salesforce keeps expanding Agentforce

Four days before Dreamforce, Salesforce introduced a portfolio of seven named, job-ready Agentforce agents:

• Casey (customer service)
• Paige (IT and HR requests)
• Carter (shopping and checkout)
• Marshall (supply chain and back office)
• Piper (inbound pipeline)
• Fin (complex customer workflows)
• Hunter (outbound sales)

Six are generally available. Hunter is in pilot, with general availability planned for November 2026. It is the first agent on a new long-horizon runtime that lets an agent pursue a goal across days and weeks. Salesforce also announced multi-agent orchestration and, for Agentforce Coworker, AI Skills, with general availability planned for October 2026.

Companies do not ship a new agent portfolio and a new runtime for a product they are replacing.

4. AIforce adds a layer on top of Agentforce

Salesforce’s AIforce announcement describes the company’s architecture as four layers:

1. Data 360 for unified data.
2. Customer 360 for applications and business logic.
3. Agentforce as the digital workforce.
4. AIforce, a new layer that brings that whole foundation to any AI interface.

Claudeforce is one of AIforce’s three interfaces. In Salesforce’s own framing, AIforce sits on top of Agentforce rather than replacing it.

The same announcement says Agentforce Coworker, another AIforce interface, can call the Agentforce agents you have already built. The interfaces and the agents are designed to work together.

5. They run on the same foundation and permissions

Salesforce in Claude reaches Salesforce through the Headless 360 MCP server, where every action runs as the signed-in user under their existing permissions. Agentforce agents run inside Salesforce under their own configured permissions. Both route actions through Salesforce, so validation rules and business logic apply either way. You are not choosing between two data stacks. You are choosing how a given piece of work is started and supervised.

Where each fits across the sales and service lifecycle

The clearest way to see that Agentforce and Salesforce in Claude complement each other is to map them against the stages of a customer relationship. Agentforce’s job-ready agents cover the stages where work should happen without an employee prompting it. Salesforce in Claude’s skills cover the stages where a seller or manager is doing the thinking and needs the data assembled quickly.

The pattern is consistent. Agentforce owns the edges of the business, where volume is high, timing is unpredictable and customers or employees need an answer without waiting for a person. Salesforce in Claude owns the middle of the sales cycle, where a seller’s judgment matters and the bottleneck is gathering and synthesizing information.

One deal, two routes: a worked example

Here is how one opportunity might move through both, using capabilities Salesforce and Anthropic have described. It is illustrative, not a prescribed workflow.

11 p.m., Tuesday. A procurement manager at a mid-sized logistics company fills in a demo request on your website. Nobody is online. Piper, the inbound pipeline agent, engages the lead, asks qualifying questions and books a discovery call on the account executive’s calendar. This is autonomous, customer-facing work, which is exactly where Agentforce belongs.

8 a.m., Wednesday. The account executive opens Claude. The daily briefing shows the new meeting alongside deals closing this month and unread customer email. She asks Claude to prep her for the call. The call-prep skill pulls the lead record, the account, any existing contacts and recent activity into a brief with suggested discovery questions. This is employee-driven work, where Salesforce in Claude fits.

After the call. She pastes her notes and asks for a follow-up. Claude drafts the recap email and proposes CRM updates: a new opportunity, two contacts and a next step. Each change appears for approval before it is written to Salesforce.

Mid-quarter. Her manager asks Claude to prepare the team pipeline review. The deal appears with a health score, and a risk is flagged: only one stakeholder has been engaged. The account executive runs a deal review, which drafts a mutual close plan and suggests the missing stakeholders to add as contact roles.

After signature. When the customer’s team starts asking product questions through your help site, Casey handles routine questions and escalates complex ones to your service team.

At no point does one product replace the other. Agentforce handles the moments when nobody from your company is present. Salesforce in Claude makes the people who are present faster.

What did change

“Nothing changed” would be the wrong conclusion. Several things shifted in ways that matter for planning.

Salesforce’s interface is now optional

Salesforce’s AIforce announcement says people no longer have to come to Salesforce to get work done, because Salesforce now comes to them in Claude, Slack or Lightning. Stokes has said the value of Salesforce is in its data, metadata and encoded workflows rather than its user interface. For employees, the question “where do I use Salesforce?” now has several answers.

Claude became the default model on the employee-facing side

Claude now powers Slackbot, Agentforce Coworker and Salesforce in Claude by default. For many employees, the AI they interact with every day, whichever front door they use, will be Claude.

Salesforce now has its own reasoning model

Koa is Salesforce’s first CRM reasoning model, built by post-training NVIDIA’s Nemotron 3 Super on synthetic enterprise scenarios. Salesforce says it matches or beats leading models on CRM actions with three times fewer errors, according to its own CRM benchmark. Koa runs on Salesforce’s infrastructure and is available to select pilot customers in Agentforce, with general availability expected this winter in US regions.

As TechCrunch reported, before Koa, Agentforce routed multi-step reasoning to frontier models such as Claude or ChatGPT. Koa gives Agentforce an in-house option for CRM tasks. Until Salesforce says otherwise, treat it as an additional model choice, not a replacement for Claude or others. Agentforce already lets admins set a default model for the org and override it per agent.

Some seller tasks now have two routes

There is real overlap. Agentforce for Sales has offered features such as automated account research and prospecting in 2026 releases, and Salesforce in Claude now offers account research and call prep in Claude. Where the same task can be done both ways, two questions decide the route: where does the seller work, and should the task run on its own (Agentforce) or on request (Claude)?

Pricing is moving toward consumption

Agentforce is increasingly billed per action through Flex Credits. Salesforce’s help documentation lists one standard action at 20 Flex Credits, or $0.10. Salesforce in Claude is charged through Salesforce’s headless consumption model plus a separate Claude subscription, which Stokes acknowledged cannot yet be bought on a single contract. Both point the same way: paying for AI work done rather than for seats.

How control and governance differ

Because Agentforce and Salesforce in Claude handle different kinds of work, they are governed differently. Understanding the difference helps you decide which one a given task belongs to, and what your admin and security teams need to set up.

The practical takeaway: autonomous agents need more upfront design, because they act without a person checking each step. Testing, guardrails and escalation paths matter most. Salesforce in Claude needs more attention to permissions, because it amplifies whatever access each user already has. In both cases the foundation is the same: clean permissions, sensible sharing and accurate data. Our guide to running AI agents safely with permissions, data boundaries and human-in-the-loop controls covers both sides.

The naming changes, explained

Part of the “Agentforce is going away” story comes from renaming. Salesforce reverted several application names that had carried the Agentforce prefix, while the Agentforce platform itself kept its name. Salesforce Ben’s coverage of the Dreamforce ’26 Service keynote notes that, a year after Agentforce Service was introduced, Salesforce is sticking with the Service Cloud name.

What this means for your roadmap

If you have already invested in Agentforce

Your investment is not stranded. Agents you built keep running, and Coworker can call them. As Koa moves toward general availability, review whether Claude or Koa should be the model for specific agents. Look at the new job-ready agents before building your own from scratch.

If you are evaluating Salesforce AI for the first time

Start with the work, not the product. Customer-facing or unattended work points to Agentforce. Employee-driven work points to one of the AIforce interfaces, chosen by where people already spend their day. Many companies will use both. If you are planning a new implementation, our article on whether a Salesforce implementation should include Agentforce from day one walks through the timing decision.

If your sellers already use Claude

Salesforce in Claude is the quickest way to put Salesforce context in front of them, provided you meet the beta requirements: the latest Sales Cloud Enterprise edition and a paid Claude plan.

Questions to ask your Salesforce account team

Much of this is new, and details are still settling. Before you commit budget, get clear answers to these:

1. Is our org eligible for the Salesforce in Claude beta, and does the beta support sandbox orgs for testing?
2. How will Salesforce in Claude usage count against our API allowance, and can Salesforce and Claude costs be combined on one contract yet?
3. Which of the seven job-ready agents are included in our current Agentforce licensing, and which require new licenses or Flex Credits?
4. When will Koa be available in our region, and can we set it as the model for specific agents?
5. Will our users’ Agentforce Coworker activity consume seats or Flex Credits under our current agreement?
6. What is the timeline for service, marketing and commerce skills in Salesforce in Claude?

Whatever you choose

All of these options read and act on Salesforce under your existing permissions. Clean up permissions, sharing and core opportunity data before any of them goes live.

Frequently asked questions

Does Claudeforce replace Agentforce?

No. Claudeforce is the partnership between Salesforce and Anthropic, and its first product, Salesforce in Claude, lets employees work with Salesforce data inside Claude using 37 prebuilt sales skills. Agentforce is Salesforce’s platform for AI agents that work autonomously or deal directly with customers. The two serve different kinds of work on the same data, permissions and business logic. Claude even runs inside Agentforce as a reasoning model, and Salesforce launched seven new job-ready Agentforce agents in September 2026, the same month Salesforce in Claude entered beta.

Is Agentforce being discontinued?

No. Salesforce is expanding Agentforce, not winding it down. In September 2026 it announced seven job-ready agents, including Casey for customer service, Piper for inbound pipeline and Hunter for outbound sales. It also introduced a long-horizon runtime that lets agents pursue goals across days and weeks, and multi-agent orchestration. The same month, Salesforce unveiled Koa, its own CRM reasoning model built specifically for Agentforce. The Agentforce prefix was dropped from some application names, but the agent platform itself kept its name and continues to grow.

Is Claudeforce part of Agentforce?

No. Claudeforce is the broader Salesforce and Anthropic partnership announced on August 26, 2026, and it runs in two directions. One part puts Claude inside Salesforce products, including Agentforce, where Claude serves as a reasoning model for the Atlas Reasoning Engine. The other part puts Salesforce inside Claude through the Salesforce in Claude plugin. Claudeforce is also one of the three interfaces in AIforce, Salesforce’s new interface layer, alongside Slackforce and Agentforce Coworker. So Claudeforce and Agentforce overlap, but neither is a subset of the other.

Does Agentforce use Claude?

Yes. Claude is available in Agentforce as a reasoning model for the Atlas Reasoning Engine, powers Agentforce Coworker and Agentforce Vibes by default, and can be selected in Agent Builder. Salesforce says Claude is the first model provider fully integrated within the Salesforce Trust Boundary, through Amazon Bedrock. Admins can still choose other supported models at the org level and override the choice for individual agents. Salesforce’s own CRM reasoning model, Koa, is also in pilot for Agentforce, giving teams another model option for CRM tasks.

Will Koa replace Claude in Agentforce?

Salesforce has not said so. Koa is Salesforce’s first CRM reasoning model, built by post-training NVIDIA’s Nemotron 3 Super on synthetic enterprise scenarios. By its own benchmark, Salesforce says Koa makes three times fewer errors than leading models on CRM actions. It is in pilot for Agentforce, with general availability expected this winter in US regions. The safest reading is that Koa becomes an additional model choice for CRM-specific reasoning, while Claude remains the default for Coworker, Slackbot and Salesforce in Claude.

Should we choose Agentforce or Salesforce in Claude?

Choose based on who starts the work and where it happens. Agentforce fits autonomous or customer-facing work, such as answering service questions, qualifying inbound leads overnight or running back-office processes without someone prompting each step. Salesforce in Claude fits sellers who want to do their own work inside Claude, such as call prep, deal reviews and forecasts, with approval before each change. Many teams use both: Agentforce for unattended work, and Salesforce in Claude for account executives and managers who already work in Claude.

Why was Agentforce removed from Salesforce product names?

Around Dreamforce 2026, Salesforce returned several application names to their previous forms. Agentforce Sales became Sales Cloud again and Agentforce Marketing became Marketing Cloud, with Service Cloud and Commerce Cloud following the same pattern. Trade coverage reported that the newer names had confused buyers trying to match them to the products their teams already used. The change affected application names only. Agentforce, the AI agent platform, kept its name, and its features within those applications continue to be developed. If you see both names in documents, they refer to the same products.

What happens to our existing Agentforce agents?

They keep running. Nothing in the Claudeforce or AIforce announcements retires existing Agentforce agents or changes how they are configured. Agentforce Coworker, one of the three AIforce interfaces, can call the specialized Agentforce agents you have already built, so your existing work becomes reachable from more places. As Koa approaches general availability, review which model each agent should use. Compare your custom agents with Salesforce’s new job-ready agents before building anything new from scratch, since a prebuilt agent may now cover the same job.

Can Salesforce in Claude and Agentforce do the same tasks?

Some seller tasks overlap. Agentforce for Sales has offered automated account research and prospecting in 2026 releases, and Salesforce in Claude now offers account research, call prep and pipeline review inside Claude. The difference is how the work starts and who supervises it. Agentforce agents can run on their own, triggered by events or goals. Salesforce in Claude runs when a seller asks and, by default, asks for approval before writing changes. Choose based on whether the task should run unattended or on request.

How is Agentforce priced compared with Salesforce in Claude?

Agentforce is increasingly billed per action through Flex Credits. Salesforce’s help documentation lists a standard action at 20 Flex Credits, or $0.10, with credits sold at $500 per 100,000, alongside per-user license options. Salesforce in Claude has no single price. You need a paid Claude plan and an eligible Sales Cloud Enterprise edition, and Salesforce charges usage through its headless consumption model, contracted separately from Claude. Both point toward paying for AI work done rather than paying purely for seats.

Plan your Salesforce AI roadmap with us

HyphenX Solutions implements Agentforce and helps teams pilot Salesforce in Claude, Coworker and Slackforce, starting from a readiness review of your data and permissions. Talk to our Salesforce Agentforce services team to map the right mix of agents and interfaces for your business.