Studio Web is moving RPA and app projects to your local machine - here's what's coming

News Product News
1

Studio Web is evolving how automations are edited and debugged.

UiPath Assistant is now required to edit and debug RPA workflow and app projects in Studio Web. During the grace period, you can continue using the Cloud setup. After the grace period ends, the Cloud setup is no longer available and local setup is required.

  • Community users: Grace period ends July 22, 2026
  • Enterprise users: Grace period ends February 1, 2027

Studio Web will now use the UiPath Robot (Assistant) installed on your machine to view, design, and run workflows. This means RPA workflows and app projects will soon leverage your local machine instead of cloud-provisioned machines, delivering faster performance, fewer design-time errors, and a more stable experience overall. It also unlocks new capabilities that go beyond RPA, including Windows and desktop automation support (coming soon) and an improved macOS experience.

All you need is UiPath Assistant 26.0.190+ to be installed and running on your machine, with a one-time setup to get started.

See it in action:

Kapture_2026-04-16_compressed

Why we’re excited about this

This is a big step forward for the Studio Web experience. Here’s what it unlocks:

  • Faster run and debug cycles - no more waiting for cloud machines to provision. Your local hardware does the work.
  • Full hardware access - no cloud limitations on what your machine can do.
  • Windows and desktop automation support (coming soon) - scenarios that cloud execution simply cannot handle.
  • Improved macOS experience - faster and more reliable UI Automation workflows, including macOS UI automations.
  • Fewer design-time errors - reduces cloud connection dependencies for a more stable design experience.
  • Terminal access - work with local files directly from Studio Web.

What will you need to do?

A one-time setup is required:

  1. Install or update UiPath Assistant (macOS) or Robot 26.0.190+ (Windows)
  2. Open Assistant and sign in to the same organization as your Studio Web account
  3. Allow browser permissions when prompted (Chrome/Edge) or install the UiPath browser extension (Safari)

Once connected, Studio Web detects Assistant automatically every time you open an RPA workflow or app project. No repeated setup needed.

What happens when you open an RPA workflow or app project?

Studio Web will check for a connected Assistant. If it’s not set up yet, you’ll see a guided setup banner that walks you through the steps. If Assistant is already running, you’ll see a brief connection check and you’re good to go.

Supported platforms

This setup works on Windows and macOS. Linux, mobile, and tablet are not supported for RPA workflow and app projects.

We want your feedback

We want to get this right, and your input matters. Before we roll this out, we’d love to hear from you:

  • Do you already have UiPath Assistant installed?
  • Do you foresee any blockers with installation, browser permissions, or licensing in your environment?
  • What questions do you have about this change?

Share your thoughts in this thread or send feedback directly from Studio Web using the Feedback button in the upper right corner.

2

Interesting! The scope of

UiPath Robot (Assistant) installed on your machine to view, design, and run workflows

seems about execution and runtime. Great to devolop against on-prem resources indeed.

But I would love to see a design-time scope as well: To edit files locally, and have Studio Web recognize these changes.

Could you clarify if

UiPath Robot (Assistant) installed on your machine to view, design, and run workflows

(emphasis mine) already covers local coding-agent development?

Your upcoming product uip will be the step towards a “headless Designer”. I am intersted how Studio Web fits in.

3

Studio web will still be the tool to visualize Agents, Maestro, API Workflows, RPA, etc. So you can use the headless experience, combined with the local workspace and have full/live view of what the agents generate on your machine.

5

Hi @alexandru,

This sounds like a useful approach, especially for developers working with local files and on-prem resources.

I have one practical question: when Studio Web is connected to the local workspace, will changes made locally be reflected immediately in the Studio Web visual designer, or will the workflow need to be refreshed/synced manually?

Also, will this local workspace support debugging and testing workflows against local applications directly from Studio Web?

This would make the combination of Studio Web + local development + headless experience very useful for real-world RPA development.

6

Hi @Natalia_Constantinescu

the local execution part is great, specially the faster debug cycles and windows automation coming

on the enterprise side, im trying to plan ahead for phase 2 and the question i keep getting internally is about the attended license, will each Studio Web developer need one on their own machine? asking because it affects how we size things before the rollout

and just as a heads up from a big company setup, installing Assistant and allowing browser permissions usually goes through IT policy and vdi images here, so having a good heads up before the opt out window would help a lot on our side

7

Hey @Michael.Vornes, I have some good news.

We’ve managed to remove the need for a license while using Studio Web with a local setup. No need to worry about this one.

On your other topic, we will have a visible in-product countdown ribbon that will be displayed 2 months before enforcement date (February 1st).

8

Hi @Natalia_Constantinescu thats great news!!