UiPath Documentation
activities
latest
false
UI Automation activities

Remote UI Automation design (Live authoring)

Design UI Automation workflows against a remote unattended robot using a live view of its screen in Studio.

Live authoring lets you design UI Automation workflows directly on a remote unattended robot. Instead of indicating elements on your local machine, you indicate them on a live view of the robot's screen, so the workflow is designed in the same environment where it runs.

Availability: Live authoring is available starting with UiPath Studio 2026.10 LTS and UiPath.UIAutomation.Activities v26.10.7.

Why use Live authoring​

  • Design in the environment where the workflow runs - The robot machine can differ from your local machine: it may have different applications, permissions, or unexpected pop-ups. Indicating on the robot machine helps you find these differences while you design, not when the workflow runs.
  • No extra network setup - The remote screen is streamed to Studio, so you don't need to open ports or bypass network security to get a remote desktop connection.
  • Free up your local machine - The workflow project stays on your machine. Only the UI Automation design-time actions run on the remote machine, so you can keep working locally while the robot machine is used for design.
  • Use with coding agents - A coding agent can use the same remote connection to design and debug automations on the robot machine, using the CLI. See Use Live authoring with coding agents.

How it works​

When Live authoring is on, every indicate action runs on the remote machine:

  1. Studio Desktop opens a live view of the remote screen, docked in a Remote View panel.
  2. You indicate the element directly on the live stream.
  3. The UI Automation host running on the remote machine resolves the element and the selector.
  4. The result is written to the activity target, as if you had indicated the element locally.

Prerequisites​

  • Studio Desktop 2026.10 LTS.
  • Robot 2026.10 LTS should be installed on the unattended robot.
  • The UiPath.UIAutomation.Activities package version 26.10.7 or later.

Turn on Live authoring​

  1. Configure remote session for the remote machine you want to use as the design machine.
  2. In the Remote Session Settings, select Unattended Robot connection type, then Live authoring and turn remote session on.

If you run a workflow from Studio, it also runs on the local machine while Live authoring is on.

The UI Automation process on the remote machine starts as soon as the Live authoring session connects, so the first indicate doesn't have to wait for it.

Indicate on the remote machine​

Use the same entry points you use for local indicating:

  • The app card of Use Application/Browser
  • The Indicate and Edit options on the target menu of an activity such as Click
  • The Edit Screen and Edit Element options in the Object Repository

While Live authoring is on, the labels of these entries end with (remote), for example Indicate on screen (remote). The suffix disappears when you turn Live authoring off. You don't need to restart Studio or reload the project.

When you start a remote indicate:

  • The Remote View panel opens and takes remote control of the remote machine.
  • An information bar in Studio shows the progress. First it reads Please wait while we start the UI Automation process on the remote machine, then UI Automation selection is active on . The bar closes when the action ends, whether you select an element, press Escape, or an error occurs.
  • You select the element on the live stream and confirm, as you would locally.
  • When the action ends, the view returns to the panel and remote control returns to its previous state.

Actions that run on the remote machine​

With Live authoring on, the following run on the remote machine:

ActionWhere
Indicate application, target, and anchorRemote
Edit target and descriptorRemote
Highlight a targetRemote
Extract Data wizardRemote
Get Text preview and test data extractionRemote
Extract Form Data field discovery (Discover fields on remote)Remote
Change informative screenshotRemote

Informative screenshots​

Informative screenshots taken on the remote machine are transferred to the .screenshots folder of your local project. App cards and targets show them in Studio exactly as they do after a local capture.

To change a screenshot, select Change informative screenshot from the target menu. The capture runs on the remote machine. Press Escape in the remote view to cancel the capture and keep the existing screenshot.

Work with the remote view​

  • Full screen. Select Full screen in the remote view toolbar to stream the remote screen full screen. If you close a selection while the view is full screen, the next remote indicate also opens full screen and returns to the panel afterwards. If you leave full screen before the selection closes, the next indicate opens in the panel.
  • Remote control. The view takes remote control during an indicate and restores your previous setting when the action ends. When remote control is off, keyboard input, including Escape, doesn't reach the remote machine. Take control to send keys to the remote machine.
  • Cancel an action. With remote control on, press Escape in the remote view to cancel an indicate or a screenshot capture on the remote machine.

Run one action at a time​

Only one indicate-style action runs at a time, locally or remotely. This applies to indicate, the Table Extraction wizard, the Get Text preview, and test data extraction. If you start a second action while one is running, Studio refuses it and shows a message. Finish or cancel the running action first.

Use Live authoring with coding agents​

The remote connection is shared between Studio and the CLI. A coding agent can use the CLI to:

  1. Connect to the remote machine you configured in Orchestrator.
  2. Capture UI snapshots of the remote machine to find the window and the elements to automate.
  3. Configure targets for those elements. The workflow and the targets in the Object Repository are created in your local project.
  4. Run the automation on the remote machine and confirm that it works.

The project and the agent's reasoning stay local. Only the CLI calls run on the remote machine. You can run several coding agents on several projects in parallel, each using its own remote machine.

Because the connection is shared, you can open the live view in Studio to see what happens on the remote machine, for example when the agent is stuck. You can also indicate an element yourself from the workflow designer and then let the agent continue.

Troubleshooting​

A second action is refused. Another UI Automation action is already running on the remote machine. Finish or cancel it, then start the new one.

The first remote command takes a long time or fails with a connection timeout. Make sure the remote machine is reachable and that the unattended robot is connected in Orchestrator. If the remote UI Automation process stops before it is ready, Studio now returns an error that describes the cause instead of waiting for a generic timeout.

Known limitations​

Studio Desktop is the supported design experience.

Was this page helpful?

Connect

Need help? Support(opens in new window)

Want to learn? UiPath Academy(opens in new window)

Have questions? UiPath Forum(opens in new window)

Stay updated