Workday Ships Developer Agent, Agent Passport at DevCon 2026

Anyone who has ever debugged a payroll run at 3am knows the specific dread of an automated job that "helpfully" corrected the wrong field. That is the exact fear Workday is pitching against this week in Las Vegas. The company rolled out three new pieces of Workday Build aimed at developers who want to put agentic AI anywhere near an HR record or a general ledger.

What Happened

On June 2, 2026 at Workday DevCon in Las Vegas, Workday (NASDAQ: WDAY) announced three additions to Workday Build, the platform it uses to let developers ship custom AI apps and agents on top of the Workday tenant. The three pieces are Developer Agent, Agent-Ready Tools, and Agent Passport, and each targets a different failure mode of enterprise agentic AI.

Developer Agent is the IDE-side piece. It plugs into the agentic coding tools developers already run: Claude Code, Cline, Codex, Cursor, and Google Antigravity. Instead of learning a new interface, a developer types plain-English requests, and the agent scaffolds Workday apps and custom agents using the open AgentSkills standard called Skills.md. Workday claims setup that used to take days can now happen in minutes, as PR Newswire reported.

Agent-Ready Tools are the runtime piece. Hundreds of them ship across Workday, exposed over Model Context Protocol, and they carry the tenant's existing security model, delegation rules, business process controls, and audit trail with them. Developers can extend the surface with thousands of pre-built Pipedream connectors when agents need to reach outside Workday.

Agent Passport is the compliance piece. Every agent gets tested against the OWASP LLM Top 10, NIST AI RMF, and MITRE ATLAS, then earns digital stamps from independent attestation partners. Cisco is the first such partner. Developer Agent and Agent-Ready Tools are available now to early access customers through Workday Extend Professional, with GA slated for H2 2026. Agent Passport hits early access in H2 2026 with GA before year-end.

Technical Anatomy

Strip the marketing and there is a real architecture here. The stack has three layers, and each maps to a well-known failure mode from production incidents I've seen in fintech and HR-tech deployments.

Layer one is authoring. Developer Agent sits inside the developer's existing agentic IDE and generates Skills.md manifests. Skills.md is an open standard, which matters. If Workday had invented a proprietary DSL, adoption would stall inside the first quarter. By meeting developers where they already work (Cursor, Claude Code, Codex), the friction to try it approaches zero. The uncomfortable read: the choice of tooling also means Workday is now downstream of whatever prompt injection surfaces exist in those IDEs. If Cursor ships a bad update, Workday inherits the blast radius.

Layer two is action. Agent-Ready Tools are described as a new class of connector, purpose-built for autonomous agents rather than data integrations. In practice that means richer semantic descriptions, tighter parameter validation, and business-logic-aware endpoints. Workday specifically calls out reduced hallucination and latency, which is what you'd expect if the tool descriptions carry structured context instead of dumping raw REST schemas at a model. The design uses MCP, which means agents built with any MCP-aware client (including Claude) can call these tools without a custom SDK.

Critically, agents inherit Workday's security and delegation model automatically. That means if user Alice can't approve expenses over $10k, neither can an agent Alice deploys. Business process controls and audit trails come along by default. This is the correct default. Most agent frameworks I've reviewed treat authorization as an afterthought and end up with service accounts that can do anything.

Layer three is verification. Agent Passport runs continuous testing against three public frameworks and gets third-party attestation from Cisco. Continuous is the operative word. Static compliance stamps age like milk. If Passport actually re-runs OWASP LLM Top 10 checks against every deployed agent version, that is meaningful. If it stamps once at deploy time and forgets, it is theater.

Who Gets Burned

Three groups have some rethinking to do this quarter.

First, the DIY agent frameworks inside large Workday customers. I've watched teams spend six to nine months building an internal agent platform to wrap Workday APIs, and the business case is now shakier. If Workday ships hundreds of Agent-Ready Tools with inherited auth and audit, the buy-versus-build math shifts hard toward buy. Platform leads who greenlit an internal wrapper in 2025 will get uncomfortable questions in Q4 planning. Bharath Srinivas at Accenture is already publicly framing this as a way to co-create "knowledge-encoded agents" with clients, which tells you where the consultancy money is moving.

Second, the single-developer shops. Jules Mayberry is described as the only developer at Waste Connections, and her quote is telling: Developer Agent gives her "a real starting point" on top of existing Extend apps. On a ten-person IT team, one developer trying to hand-roll agents on top of raw Workday APIs is a burnout risk. Removing days of setup per agent is not a small number. That is roughly one FTE-equivalent of throughput reclaimed on a team that ships four to six custom apps a year.

Third, the compliance-and-security vendors who thought they had a clear runway to sell standalone AI governance tools into Workday shops. Cisco just got named as the first attestation partner. If the Passport model expands, third-party AI-GRC vendors will need to become attestation partners or watch procurement bypass them entirely.

My take: the biggest exposure sits with any team currently running agents against Workday data with service accounts and no audit trail. When Agent Passport hits GA, security teams will start asking why internal bots don't carry stamps. That conversation is easier to prepare for than to react to.

Playbook for AI Development

Concrete moves for platform leads and CTOs this week:

One, inventory every existing script, bot, or agent that hits Workday APIs today. Note the auth mechanism (service account vs delegated), whether calls are audited, and who owns the code. This inventory becomes your migration list once Agent-Ready Tools hit GA.

Two, if you use Cursor, Claude Code, Codex, Cline, or Google Antigravity in your dev org, get on the Extend Professional early access list now. The value of Developer Agent depends on your team's fluency with the underlying agentic IDE, and fluency takes weeks, not days.

Three, treat Skills.md as a portable artifact. Even if you never ship to Workday, the AgentSkills standard is worth reading. Open standards for agent capabilities are still shaking out, and betting on one that a $60B+ platform vendor is publicly backing is a reasonable hedge.

Four, pre-write your Agent Passport policy. Decide now which OWASP LLM Top 10 categories are hard blockers for production deployment in your org, and which are warnings. When Passport goes GA, you want a policy document ready, not a debate.

Five, budget for the migration. Retrofitting existing custom apps to use Agent-Ready Tools instead of raw APIs is not free. Assume roughly one sprint per non-trivial app. Verdict: start the inventory this week or pay double later.

Key Takeaways

• Workday shipped three pieces at DevCon on June 2, 2026: Developer Agent (authoring in Cursor, Claude Code, Codex, Cline, Antigravity), Agent-Ready Tools (runtime over MCP), and Agent Passport (verification against OWASP LLM Top 10, NIST AI RMF, MITRE ATLAS).
• Agents inherit Workday's existing security, delegation, business process controls, and audit trail by default, which fixes the #1 failure mode of internal agent frameworks.
• Cisco is the first Agent Passport attestation partner, signaling that AI-GRC is being folded into the platform rather than left to standalone vendors.
• GA timing: Developer Agent and Agent-Ready Tools in H2 2026, Agent Passport before end of 2026. Early access is live now via Workday Extend Professional.
• Platform leads should inventory existing Workday-touching bots this quarter and pre-write their Passport policy before GA lands.