UiPath 26.0.195 June Community Release

News Release Notes
1

Studio

Tailor Studio with extensions

Studio now supports extensions, letting you add file viewers, editor tools, and other capabilities to support how you actually work on automations.

Why

Building an automation means juggling more than just workflows. There’s the PDD to reference, the input spreadsheet to check, the API to test before you wire it up or coding agents to help you with development. All of it lived outside Studio - and getting to it meant leaving what you were doing.

The goal was simple: bring the tools and files you’re already working with into the same environment as your automations, without asking you to change how you work.

How

Studio now supports extensions and the Extensions panel is where you find, install, and manage them.

Inside the panel

  • A curated Recommended set built around RPA workflows

  • A view of the Installed extensions so you always know what you have available

  • Full access to the Open VSX catalog beyond the Recommended set

  • Install custom extensions directly from a .vsix file

Worth knowing

The Recommended set is a starting point. We’ll keep adding extensions as we find ones that genuinely improve the Studio experience.

What you can do

A few things to start - the catalog goes much further:

  1. Add a coding agent. Install Claude Code or any other coding assistant available and get help building, editing, and reviewing automations without leaving Studio.

  2. Test your integrations before you build them. Install Postman and test your endpoints from inside Studio — response schema, authentication, payload structure — before a single activity is placed on the canvas.

  3. Open your reference material next to your workflow. Install Office Viewer and PDF for VS Code to read the PDD, check the sample invoice, or review the input spreadsheet inline - without opening another app.

  4. Keep your process map inside the project. A Mermaid diagram in the repo travels with the code and stays current. Install Markdown Preview Mermaid Support and it renders right there in the Markdown preview.

  5. Keep your installation tidy. Search the catalog, install in one click, remove just as easily. Only what you actually use.

  6. Shape your workspace. Show or hide panels introduced by Extensions - and other panels - to keep focus on what you’re working on.

Demo: testing an API with Postman

Demo: coding assistants in Studio

Demo: reading project documents in Studio

Try it

Open the Extensions panel and browse the Recommended set as well as the full set of extensions.


Worked well? Drop a reply with what you installed — the best finds from the community end up in the Recommended set.

Something missing? Build it. Any VS Code extension packaged as a .vsix installs directly in Studio - if you’ve built something useful for your team, share it in this thread.

What are you going to try first? :backhand_index_pointing_down:

2

Dropping so many features, at this point studio can order me a coffee when there’s a latenight bug in codebase!

3

Here my first extension for the UiPath Studio Desktop.

I might release the extension for users with a Community license.

5

I gave the extension a deep dive this weekend, and probed how far I can push standard VS Code extension capabilities.

  1. Command Palette — Ctrl+Shift+P is the primary command discovery surface in VS Code. Without it, every command needs a bespoke UI entry point. ~95% of extensions assume it exists.

  2. Host identity API — vscode.env.appName returns “Visual Studio Code” inside Studio. Extensions cannot detect which host they’re running in and cannot adapt behavior. A stable vscode.env.appHost value (or equivalent) is needed for cross-host compatibility.

  3. some guidance would be helpful how far UiPath plans to push this as a “platform” for OpenVX extensions. Because I soon ran into questions like contributes.configuration / vscode.workspace.getConfiguration() when attemtping to persist user settings via the standard configuration API.

I have dozens of ideas and they have in common: They are not generic VS Code extensions, but would interact with the opened project in one way or another.

Here a port of my widget:

image
image1024×784 86.1 KB

The power of extensions lies in the authenticated Studio user and the Orchestrator API connection.

@alexandru @loginerror

6

hi @cprima , so glad to see this! Is this available in the Open VSX library? If not, maybe we can connect about this as well as your questions.

7

Hi @Raluca_Laic

I will find some time this weekend to follow up on
Looking for a DevRel contact — Section 4.e interoperability process - Help / Studio - UiPath Community Forum

Because I want to do things properly, and a VS Code extension working against the object repository is interoperability in the sense of “software legalese”.

I have many such workstreams going on, but little time. It is my motivation though to showcase how the new Studio features can be used to the max.
And a .vsix extension is on my todo list.

My build pipeline towards OpenVSX and VS Code marketplace is already working. The legal stuff is the next big milestone.