You will learn what the three AIforce applications are, what each does with Salesforce data, and what the Claude Code plug-in adds for developers.
Why read this
The piece is a brief overview without implementation detail.
AIforce initial release
Claudeforce
Slackforce
Agentforce Coworker
The initial AIforce release is made up of three applications
Salesforce announced AIforce at Dreamforce, a set of applications that connect platform data and workflows to Claude and Slack. The initial release has three parts: Claudeforce, Slackforce and Agentforce Coworker. Claudeforce comes out of an expanded partnership with Anthropic and ships with 37 pre-installed sales capabilities, from prospecting to opportunity management, plus a Claude Code development add-on with more than 40 further tools. Deloitte, GitLab and Legora piloted it, and it is now in beta for all customers.
Slackforce brings Salesforce data into Slack conversations, letting teams combine information from different sources, apply filters and take actions through interactive surfaces. The upgraded Slackbot assistant and Slack CRM feature can update files and create records from simple text commands.
Agentforce Coworker works inside Salesforce’s internal Lightning environment as a digital assistant that uses customer history and activity. According to the company, it needs no data migration or new permission settings, and it recorded 100,000 activations in its first 35 days.
Readers will learn how to configure the Salesforce in Claude plugin, audit permissions for agentic access, and prepare for the November billing model using Flex Credits and agent registration.
Audit Permission Sets and profiles
Clean the fields the skills read
Keep approvals on
Pilot in a sandbox
Name an owner for connections
Five checks to prepare your Salesforce org for Claudeforce and AIforce billing
Claudeforce, the expanded Salesforce and Anthropic partnership announced on August 26, 2026, works in two directions. Claude becomes a reasoning model inside Agentforce and the default model in Slack, while Salesforce reaches into Claude through the Salesforce in Claude plugin. That plugin bundles 37 prebuilt sales skills covering account research, call prep, pipeline review and CRM updates, with Salesforce and Slack connectors. It is in beta for approved orgs on paid Claude plans and requires the latest Sales Cloud Enterprise edition.
On security, sellers sign in with their own Salesforce credentials, so Claude can only do what their permissions allow, and by default it asks for approval before any write. Salesforce Help notes that when a custom action uses a Claude model hosted inside the Salesforce Trust Boundary, data stays inside that boundary, though Einstein Trust Layer data masking is disabled for those agents and zero data retention still applies. The article advises reading that page in full before writing a risk assessment, and it warns that most capability claims come from launch material and should be tested in a sandbox first.
The setup path has four stages. First, the org confirms eligibility and gets approval through the beta sign-up on AgentExchange. Second, a Salesforce admin creates an External Client App for Claude, because Connected Apps are not supported for MCP clients. Third, a Claude Primary Owner or Owner enables the plugin in Organization settings and enters the app’s consumer key and secret. Finally, each member signs in with their own Salesforce account on first use.
The billing changes are targeted for November. Admins register agents, each of which gets its own identity and can hold a narrower Permission Set than a human user. Every successful MCP or API call from a registered agent counts as a Headless Platform Interaction, paid with Flex Credits, though the rates are still TBA and metering applies only to active production orgs, with 30 days’ notice before it starts. Customers who buy on or after September 17, 2026 must register agents at purchase, while existing customers register at renewal. The article does not say how the Salesforce in Claude plugin will be classified under this model.
The article recommends five preparation steps: audit Permission Sets and Profiles, clean the fields the skills read, keep approvals switched on, pilot in a sandbox, and name an owner for connections and consumption. Cloud Odyssey’s own view is that Claudeforce exposes existing CRM data quality problems, and it suggests starting with a health check, connecting surrounding systems, piloting with one team, and keeping model choice open.