5 min Applications

UiPath CEO: Agentic AI shifts the definition of a software builder

UiPath CEO: Agentic AI shifts the definition of a software builder

With a CEO who positively likes to call software automation services “robots” just because that’s what they actually are, Daniel Dines, CEO and founder of UiPath, now states that the emergence of coding agents signals a fundamental shift in the “definition of a builder” on his company’s platform. With the new added bonus of agentic software application development builders now in the mix, the current state of programming is undergoing a fundamental shift in space and time, so where does that put us in the universe next?

Dines’ comments come on the back of his firm’s launch of UiPath for Coding Agents, a platform-wide integration enabling every coding agent to become enterprise-deployable.

The company that used to portray itself as a robotic process automation specialist now labels itself an agentic business orchestration player.

By combining coding agents with the visual orchestration of the UiPath platform, “builders” of any technical level can create, test, deploy, operate and govern enterprise automations through a natural language conversation with their coding agent of choice.

“It’s a fundamental shift,” underlines Dines. “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.”

Agents in isolation

Despite the popularity of coding agents, they still exist largely in isolation, disconnected from enterprise development workflows, security policies, code review processes and deployment pipelines. 

Connecting one agent to another (and to the enterprise systems they need to act on) remains a manual, brittle process for most teams. 

Dines and team say that without orchestration capable of connecting agents to existing CI/CD infrastructure, testing frameworks and governance controls, any coding agent outputs require manual handoffs and human intervention at almost every step. This means that hoped-for and anticpated productivity gains stay trapped inside silos and development sandboxes, never reaching an organisation’s the end to-end enterprise processes.

UiPath for Coding Agents runs with the following core functions:

  • Open Platform for Any Coding Agents – Rather than forcing enterprises to standardise on a single vendor, UiPath allows teams to run Claude Code in one department, Codex in another and adopt whichever coding agent emerges next.
  • Orchestration as Foundation – The orchestration layer is the constant, connecting into agents with observability, execution and governance as the underpinning element, regardless of the coding agent being used (current or future model version) or which developer last touched the code; as new models are released from Anthropic, OpenAI, Google (and other AI leaders), orchestration makes the platform more valuable, not less compatible.
  • Built-in Governance – Policy enforcement, audit trails, credential vaults, role-based access control, and runtime controls are standard for every automation entering the platform, regardless of whether created by human developers or coding agents, following repeatable, governed enterprise pathways from promotion through production.

Dines and team say that the open architecture of the UiPath platform ensures that better coding agents generate code, faster, with fewer errors. The resultant technology is executed against real enterprise systems, under real governance, at real scale. Crucially, automations continue running when models get replaced; developers move on and regulators conduct audits. The execution layer compounds with every model release, and the orchestration layer compounds with every new artefact built.

“For developers already building on UiPath, this integration raises the productivity ceiling. Testing, debugging and deployment become as accessible as initial development,” notes the company. “Rather than waiting weeks or months for development resources, business users can now prototype and refine automations in real time. The coding agent handles the technical complexity while UiPath ensures enterprise readiness. For millions of people who have never created automation- business analysts, process owners, and domain experts – the barrier drops to a simple conversation with their coding agent, unlocking previously inaccessible productivity gains.”

UiPath for Coding Agents is available now to enterprise customers, with initial support for Claude Code and OpenAI Codex and additional coding agent integrations planned for 2026.

Business users, let loose?

Do tools like this represent a new Wild West where we allow non-technical business users to start affecting automations inside real world workflows? Well, it’s yes and no, isn’t it? Yes business users can now start to create automations, usually within the limits of strict policy controls based upon their confirmed digital identity and privileges – and, equally, no, these same users are unlikely to start reprogramming the central profit and loss register and core operational backbone of a company as a result. That being said, we also now have to consider how much agentic programming is going to happen and whether we have locked down new copilot-driven functions in the codebase and the workplace in general. The world might be a better place as a result of all this, only time will tell.