The agent runtime is consolidating — three releases this week show enterprise default settling around audit-trail-first orchestration
Salesforce Agentforce 3, Anthropic MCP 2.0, and the Opus 4.7 launch landed in the same 72-hour window. Read together, they describe a market that is no longer asking whether agents can do enterprise work — it is asking how the per-action audit layer gets built and which runtime owns the inter-runtime handoff. The agent stack just chose its primitives.
Three releases, one shape
Salesforce shipped Agentforce 3 as the default workflow for new enterprise rollouts — not as an add-on. The audit-trail panel was the missing piece enterprise IT buyers had been refusing to deploy without. Anthropic released MCP 2.0 with cross-runtime auth handoff so a Claude-orchestrated task can route mid-pipeline through GPT-5 or Gemini 2.5 and back without losing tool state. Opus 4.7 launched as an agent-native frontier model with native long-horizon planning and tool use built into the post-training mix.
What the audit-trail piece really means
The Salesforce per-field permission model — agent can update opportunity stage but not close-date or owner — is the first serious answer to the SOX-discipline question. It maps to how enterprise change-management already works, which is the only path that gets agents past the CISO/audit committee veto. Every other agent vendor is now on a clock to ship comparable granularity.
The pricing fork sharpens
Anthropic, OpenAI, and Google bill agent runtime by tokens. Salesforce just chose to bill by verifiable business actions. That puts Agentforce on a different procurement pipeline — quota line item, not compute line item — and shifts the conversation in enterprise IT from 'how much did the agents cost this month' to 'how many billable actions did the agents complete.' The latter is a metric finance teams already understand.
The interoperability bet
MCP 2.0 is the closest the agent ecosystem has come to a TCP/IP-style interoperability standard. If it sticks, the lock-in moves from runtime to tool surface.
The cross-runtime auth handoff in MCP 2.0 is the strategic counter-move to Salesforce's vertical bet. If agents can migrate between runtimes without re-authenticating, no single model lab owns the orchestration layer — but whoever owns the connected tool surface does. That's why Anthropic shipped it now, even though MCP 1.x was working: they're racing to own the protocol before the verticals lock customers in at the workflow layer.
The forward read
- Audit-trail tooling becomes table-stakes by Q3. Every agent runtime ships per-field permission granularity or loses enterprise pipeline.
- Per-action billing spreads. At least one model lab adopts a parallel pricing tier alongside per-token by year-end.
- MCP 2.0 adoption is the canary. If three or more competing runtimes implement it within 90 days, the protocol is permanent and the orchestration battle moves up-stack.
The runtime layer just stopped being the moat. The moat is the audit layer, the action-billing pipeline, and the tool surface beneath both.
Salesforce — Agentforce 3 press release → · Anthropic — Model Context Protocol 2.0 → · The Information — Opus 4.7 agent-native release →