UiPath for Coding Agents Public Preview: Our Most Exhaustive Release Yet!

News Product News
1

Hello UiPath Community!

Earlier this year, we introduced UiPath for Coding Agents, enabling you to use a coding agent of choice (e.g. Claude Code, Codex, Cursor, Google Antigravity, etc. ) to plan, build, test, deploy, and operate UiPath-built automations across the entire lifecycle.

Today, we’re excited to introduce our most exhaustive new capabilities that let you do so much more with coding agents and UiPath - available now in public preview. Install & Get Started Now.

What can you do today? In addition to RPA, UiPath for Coding Agents now supports building, troubleshooting, and optimizing agents, Coded Apps, IXP, Solutions, API Workflows, human-in-the-loop tasks, Platform operations, Orchestrator, Data Fabric, Admin, Governance, testing scenarios with Test Manager and Audit tools.

How can you get started? Just run one command in your terminal or give it to your coding agent. Install & Get Started Now.

Questions, and feedback, are always welcome. Just drop us a note in the comments or reach out via the Insider Portal. We can’t wait for you to try these new capabilities.

Thank you,

Sherif and the UiPath for Coding Agents t eam

3

Next steps are in the methodology, not the product:

  • we MUST pivot hard away from PDD in docx or PDF file formats. The waiting time for Claude Code & Co to parse these is bad developer experience and burns tokens. Coding agents speak markdown and read datafiles. And can deal with coding-agent-skills executing scripts.

  • For RPA, Object Repository and App/Web Recorder must be used early in requirements management, and a “clickpath” even be based on screenshots captured early in the methodology. The “clickpath” must be part of the requirements captured in markdown.

  • .xaml MUST go away. It burns developer token budget. Why should my employer pay for token burn because of a file format inadequate for coding agents? And with maintenance also done by coding agents the fear of low RPA developer pro-code skillset is no longer valid.

  • as a result, the current coding agent skills need to be written to save my token budget, i.d. “coded automation, coded source files, coded testdata generation”.

  • Reflection is a crutch and we need a llms.txt accessible repository with at least the UiPath-official packages

Any RPA developer who in 2027 will do drag&drop is a dinosaur. It will be hard for some developer to find words: Coding agents require textual instructions. Failure to be able to describe verbally what shall be implemented will severely degrade the performance. Year-long habits to “paste a screenshot in the forum” contributed to a “silent majority” lacking vocabulary.
The job opportunities remain, with more complex usecases and thankfully better code quality.

My main feature request going forward: Redesign the serialized object repository, to make it accessible for coding agents.
That includes the object repository in library-packages!
Even if it was just a “llm-txt inspired” index manifest pointer file.
@alexandru @loginerror @Sherif

Ideally before 26.10 LTS hits the enterprise installed base.

4

Support for playwright selector harvesting and chromium support would be awesome too.

5

Thanks for the feedback @cprima . Our team is constantly working on improving the experience of UiPath for Coding Agents, and we hope to make it even better as we get closer to GA.