Salesforce AIforce, now SIforce: what it is and what admins need to do

On 9 October 2026 Marc Benioff posted that AIforce is "officially SIforce". If you searched for either name this week, you are not alone, and you are not behind: as of 14 October Salesforce had not published anything official about the rename, and Salesforce Ben reported that it was unclear whether anything beyond the name would change.

The product underneath has now had three names in about six months:

The name matters far less than what it describes. This post explains what AIforce is, which parts are available today, and the one change that will land on every admin's desk: agent registration.

We use "AIforce" below because that is the name on Salesforce's own documentation at the time of writing. When you see "SIforce", read the same thing.

What AIforce actually is

Salesforce describes AIforce as an interface layer that brings your org's data, workflows, permissions and governance to whatever AI tool people already use. Instead of opening Salesforce, a seller asks Claude or Slack, and the answer and any action still run through Salesforce's rules.

The Dreamforce announcement launched it with three pieces:

• Claudeforce. The Salesforce and Anthropic partnership, announced on 26 August 2026. Its first product, Salesforce in Claude, is a prebuilt MCP server inside Claude with 37 sales skills (meeting prep, deal health, pipeline review). Salesforce lists it as beta for all customers. A Salesforce Development plug-in for Claude Code with more than 40 skills is also part of it.
• Slackforce. Live, shared Slack surfaces, Slackbot reasoning over Slack and Salesforce context, a new Slack CRM and Slack Code. The newsroom article does not give separate dates for each piece.
• Agentforce Coworker. An AI teammate inside Lightning, switched on with a button. Salesforce says 100,000 users activated it in the first 35 days.

All three sit on the Headless Toolkit, which exposes platform features as MCP servers, APIs, CLI commands, plug-ins and skills. That is the developer-facing part, and it is the part that brings new rules.

Salesforce has not published AIforce pricing. Both the newsroom post and the press release say pricing and packaging are subject to change.

The part that affects admins: agent registration

The most useful document on AIforce is not a keynote recap. It is Salesforce's Knowledge article Understand AIforce Impact (005360285, published 17 September 2026). It says Salesforce is targeting November for three linked changes in the Headless Toolkit:

1. Agent registration ("Agentic Identity"). Admins register each AI agent on the platform. The agent gets its own identity instead of borrowing the identity of the person it is helping, and you can give it a narrower permission set than that person has. Salesforce's own analogy: issue the agent its own badge rather than lending it an employee's.
2. New security controls that come with that identity.
3. A new billing model. Every successful call a registered agent makes, over MCP or the API, is counted as a Headless Platform Interaction and consumes Flex Credits. We covered the cost side in detail in Salesforce Flex Credits for MCP and agentic API calls.

The deadlines in the article are worth reading slowly:

• New customers (purchasing on or after 17 September 2026) must register every agent that uses Salesforce APIs within three months of Salesforce's notice that Agentic Identity is available.
• Existing customers using agents with APIs must register them and move them to the new billing model at renewal.
• Any use of a Salesforce MCP server requires agent registration within three months of that notice. The article says this applies to all customers.

Two reassurances from the same article. Sandboxes, scratch orgs and Developer Edition orgs are not metered, so building and testing does not draw down credits. And "the pricing and security options for traditional integrations stay exactly as they are today": the change targets agentic traffic, not your existing middleware.

At the time of writing, the Flex Credit multiplier for a Headless Platform Interaction is listed as "TBA" and nothing is being metered. Salesforce has promised 30 days' notice before metering begins.

What to do now, before the notice arrives

You do not need to buy anything today. You do need to know what is already talking to your org.

1. List the AI agents that touch your org. Ask your developers and power users directly. Claude Code with an MCP server, Cursor, a ChatGPT connector, a custom agent built on the API: each one is a candidate for registration. Most teams find more than they expected.
2. Check connected apps and OAuth usage. In Setup, Connected Apps OAuth Usage shows which apps hold tokens and how many users authorised them. Look for anything recent that nobody told you about.
3. Decide what each agent actually needs. Registration lets you give an agent less access than its user. That only helps if you know the minimum. Write it down per agent: which objects, read or write, which environment.
4. Separate testing from production. Since sandboxes and Developer Edition orgs are not metered, point experiments there. Production should see only agents you intend to register.
5. Find out where you stand on Flex Credits. The article's first step is making sure the org is enabled for Flex Credit billing, for example through Salesforce Foundations, which it lists as available at $0. Your account executive can confirm what your contract says.
6. Put the renewal date in the calendar. For existing customers that is when the obligation bites.

Where orgadmin.ai fits

orgadmin.ai is an independent tool. It is not part of AIforce, and Salesforce has not said how it will classify third-party tools that call its APIs on a user's behalf, so we will not guess. What we can say:

• Our MCP server lets Claude Code, Codex or Claude Desktop work with your org through scoped tokens that are read-only until you add scopes, with every call checked against your workspace role and written to an audit log. That is the same "own badge, narrower permissions" idea Salesforce is now building into the platform.
• AI Org Chat answers most questions about fields, automation and code from a stored copy of your metadata. Fewer live calls to Salesforce means fewer interactions to meter once metering begins.

When Salesforce publishes the Agentic Identity documentation, we will update this post with exactly what it means for agents connected through orgadmin.ai.

The short version

• AIforce and SIforce are the same thing: Salesforce's layer for using your org from Claude, Slack and other AI tools. It used to be called Headless 360.
• Claudeforce (Salesforce in Claude) is in beta; Agentforce Coworker is available now.
• The real admin change is agent registration, targeted for November 2026, followed by Flex Credit metering of agent calls once Salesforce sets a price and gives 30 days' notice.
• Start your inventory now. Knowing which agents touch production, and what each one needs, is the work that every later step depends on.

Last checked 14 October 2026 against Salesforce's newsroom, the Claudeforce press release and Knowledge article 005360285. Product names and dates in this area are changing quickly; we will revise this post as Salesforce confirms details.