UiPath today announces UiPath for Coding Agents, a platform-wide integration designed to let enterprises run any coding agent – Anthropic’s Claude Code and OpenAI’s Codex at launch, others planned through 2026 – inside the orchestration and governance layer it already sells to large enterprises. The company describes the launch as an industry first.
Dines has been pointing toward this product across two earnings updates. In the Q4 FY2026 earnings call in March, he flagged coding agents as the next major release, describing the problem as an automation backlog growing faster than enterprises can build. At an investor product strategy session in April, he went further, describing a roadmap in which UiPath builds its platform primarily for coding agents rather than human developers. UiPath for Coding Agents is that pivot, shipped.
What’s in it
Coding agents are popular but currently isolated. They sit outside enterprise systems – disconnected from continuous integration and deployment (CI/CD) pipelines, code review, and security policy. Connecting one to another, and to the systems they need to act on, requires manual handoffs at most points. Productivity gains stay in development sandboxes. UiPath says its platform fixes that, in three ways.
First, the open architecture. UiPath isn’t standardizing on a single coding agent vendor. Claude Code can run in one department, Codex in another, and a future agent – from Google, an open source release, or somewhere else – slots in alongside without re-platforming. The orchestration layer is the constant. At launch, “any coding agent” means two of them, although UiPath says more integrations are coming through 2026.
Second, that orchestration layer itself. Maestro – UiPath’s workflow orchestrator, built on Temporal’s durable execution technology – provides the observability, execution and governance scaffolding regardless of which agent generated the underlying automation or which version of the model. Durable execution means the engine persists the state of every workflow step, so automations survive infrastructure failures and can be paused, resumed, and audited end to end. UiPath says the platform becomes more useful, not less compatible, as new model releases ship from Anthropic, OpenAI, Google and others, so that the execution layer compounds with every model release, and the orchestration layer compounds with every new automation built.
Third, built-in governance – policy enforcement, audit trails, credential vaults, role-based access control (RBAC), and runtime controls applied to every automation entering the platform, whether built by a human developer or a coding agent. The promise is that automations continue running when models get replaced, developers move on, and regulators conduct audits.
What Dines says
Daniel Dines, CEO and founder of UiPath, says:
The emergence of coding agents signals a fundamental shift in the definition of a builder on our platform. We are first to market with a platform that treats AI-generated automations as first-class citizens, with the same governance, reliability, and scale that enterprises demand. Now, anyone can describe what they want, direct a coding agent to produce it, and carry through every stage to production. It lowers the barrier to who can build, crossing the line from idea to execution. Virtually anyone—product managers, analysts, and operators—can describe what they want, direct a coding agent to produce it, and carry it through to something that actually runs.
This indicates that UiPath is no longer designing for human developers writing process automations in Studio. The primary user of the platform is a coding agent, and the human’s role becomes describing intent, exercising judgment, and approving what the agent produces.
For business users who have never written an automation – analysts, operators, process owners – the entry barrier is designed to drop to a conversation with their coding agent of choice, while UiPath handles the platform plumbing.
That pitch assumes those users already know how to have the conversation. Coding agents are powerful tools, but they are not yet intuitive: knowing what to ask, how to phrase it, when the output is wrong, and how to course-correct is a learned skill in itself which takes time and practice. For someone meeting one of these tools for the first time, the curve is steep — closer to handing someone their first smartphone than picking up a familiar tool.
For existing developers and those who have had chance to familiarize themselves with coding agents, the productivity ceiling aims to rise so that testing, debugging and deployment become as accessible as initial development. Waiting weeks or months for development resources is the bottleneck this product is designed to dissolve.
Where the governance line gets drawn
Governance is where the open-platform claim and the enterprise readiness claim meet. Policy enforcement, audit trails, credential vaults and runtime controls apply to every automation “entering the platform,” as the launch material puts it. The phrase leaves open whether governance also applies to what the coding agent does before submission – the prompting, the reasoning trace, the iterations during code generation, and the inputs the agent uses to decide what to build.
That matters more in regulated sectors. If the orchestration layer is the constant, the integrity of that constant has to extend into the workflow that produces the automations entering it: credential isolation during generation, sandboxing of agent activity, and audit capture of the reasoning process, not just the final artifact. The launch material describes the destination clearly. How UiPath governs the coding agent itself – as distinct from its output – is the piece a follow-up briefing will need to fill in. For now, UiPath for Coding Agents is available now to enterprise customers, with initial support for Claude Code and OpenAI Codex.
My take
Coding agents have spent the last year getting good at narrow problems – write this function, refactor that module, scaffold this service. They produce impressive demos. What UiPath has done today is plug that capability into its orchestration, observability and governance layers – which is exactly where most enterprise AI projects currently get stuck.
“Orchestration” is being used prolifically in enterprise software now. Almost every workflow vendor uses the word, and most have only retrofitted it into their marketing in the past year. UiPath has been using it with technical specifics for longer than most. Maestro launched in May last year, built on Temporal’s durable execution technology, with real claims about auditability and the ability to pause, rewind and inspect actions taken by agents, robots and people at each stage. All of which matters today, because the launch only holds together if orchestration is its own separate, durable layer of the stack – one worth building on. UiPath has more right to claim it than most.
UiPath has made a smart move by not building a coding agent of its own so that customers aren’t being pushed into making a choice. Enterprise AI buyers appear to be hedging across two or three model providers, refusing to lock in to any one foundation model lab. If Claude Code is stronger at long-context refactoring this quarter, and Codex is stronger at greenfield generation the next, UiPath wins both. And whichever model ships after that. It is harder to predict is whether the compounding actually lives up to it’s promise. UiPath says the execution layer gets more valuable with every model release, and the orchestration layer gets more valuable with every automation built on top of it. It sounds good on paper, and it also lines up with the software cost deflation idea Dines made the case for in March – as code generation gets cheap, durable value migrates to the layer that provides trust, integration and accountability.
There are some important dependencies I’ll be watching out for this year, including how many coding agent integrations actually ship beyond the launch pair, and how UiPath governs what the coding agents do before their output reaches the platform – the prompting, the reasoning, the credentials the agent touches during generation. Plus, whether any of the early enterprise customers will go on record about what production deployment actually looks like inside their environments.
In the meantime, this is a smart call. But the matter of how UiPath governs what coding agents do before their output reaches the platform is critical to deciding whether the whole thing actually works. An interview with UiPath on the new product is to follow in the coming weeks. Pre-submission governance – what coding agents do before their output reaches the platform – is top of the list.