ServiceNow's Brazil release routes outside agents through its workflows. Decide where agent authority lives

Every large company now has agents from several vendors: one in the CRM, one in the HR suite, a coding agent, a few built in-house. Each was approved on its own. Few organizations can say which of them may call which, or under whose authority.

ServiceNow’s Brazil release, generally available since November 5, is an offer to answer that question on ServiceNow’s platform. Its most consequential piece is not the most visible one.

Three additions, one ambition

ServiceNow frames the release around three areas.

For software teams, Autonomous Engineer takes a defined unit of work from a developer, plans it, builds in parallel with background agents, and writes and runs tests. ServiceNow is explicit that developers keep responsibility for architecture, quality and production readiness.

For the desktop, Arc, the personal agent we analyzed when it launched in October, now sits inside the release, governed by ServiceNow’s Super Intelligence Control Tower, where IT defines what Arc may access and do. ServiceNow says that in lab testing Arc handled 95% of everyday background tasks on local models running on NVIDIA RTX Spark hardware, keeping frontier models for harder work. That is a lab figure from the vendor, not a production measurement.

For the enterprise, Action Fabric connects approved ServiceNow and third-party AI agents to workflows, external tools and each other, with identity, permissions, policy and auditability applied along the way.

There is also a new interface, Lux, and more than 1,300 accessibility improvements.

Action Fabric is the strategic piece

Autonomous Engineer competes with many coding agents. Action Fabric competes for something scarcer: the position between agents.

When a Salesforce agent needs an IT ticket opened, or an in-house procurement agent needs an approval, the call has to pass through something that knows who the agent is, who it is acting for, and whether that action is allowed. ServiceNow’s pitch is that its workflow engine, which already holds approvals, assignment rules and audit history, is the natural place for that check. It extends the signed AI passport for agents that ServiceNow introduced in October: the passport says who the agent is; Action Fabric decides where it may go.

The argument is reasonable. Workflow platforms have the records auditors already trust. We have argued that the authority to commit a transaction should stay with the system that owns it, and ServiceNow owns a lot of transactions in IT, HR and customer service.

The risk is the same argument in reverse. Salesforce, Microsoft, Google and Workday each make a similar claim for their own platform. An enterprise that accepts every one of them ends up with five control layers, each authoritative for its own agents and blind to the others.

Decide the role before you connect anything

Before wiring third-party agents through Action Fabric, three decisions are worth making explicitly:

1. Which platform is the system of record for agent identity. Your identity provider, a dedicated agent registry, or ServiceNow. Pick one and make the others consume it.
2. Which actions ServiceNow authorizes, and which it only routes. Approving an IT change is ServiceNow’s job. Approving a payment probably is not, even if the request passes through it.
3. Where the audit trail is read. If an incident involves three agents from three vendors, someone has to reconstruct it from one place. Make sure Action Fabric’s logs can be exported to the security team’s tools, not only viewed inside ServiceNow.

ServiceNow customers should take the release seriously, because Action Fabric could become the cheapest place to enforce agent policy for work that already lives there. It should not become the place by default.