2026.10.0

2026.10.0 release notes for Studio.

Release date: November 12, 2026

Studio 2026.10 is the long-term support release that follows 2025.10. Its main theme is building automations together with coding agents: UiPath Autopilot, built into Studio, and third-party agents such as Claude Code and OpenAI Codex. Studio sets the agents up and gives them the context of your project, and your team gets the tools to review and ship their work: source control with visual workflow diffs, extensions, a built-in terminal, and solutions that you create, debug, and publish in Studio.

The release includes the changes released on the short-term support train since 2025.10, from build 2026.0.179 to build 2026.0.204, plus fixes made for 2026.10. Studio is now installed with the UiPath Platform Installer, official packages come from a new feed address, and new projects default to Robot 26.10 unless you choose an older Robot version. If you deploy Studio in your organization, read Deployment and administration before you upgrade.

What's New

UiPath for Coding Agents

Coding agents such as UiPath Autopilot, Claude Code, and OpenAI Codex can build and change UiPath projects with Studio, using the UiPath CLI and UiPath skills. The Coding Agents tab, under Backstage View > Tools, shows whether each agent's command-line interface (CLI) is installed, manages the UiPath CLI, and sets up each agent's UiPath skills and Studio extension.

New projects give an agent the context it needs. They include an AGENTS.md file that tells coding agents how a UiPath project is organized and which UiPath CLI commands validate, build, and run it, plus a CLAUDE.md file for Claude Code. After each package restore, Studio copies the documentation that activity packages ship into the project, under .local/docs/packages/<PackageId>/. A policy can turn off the AGENTS.md and CLAUDE.md files.

You can follow and review what an agent changes.

• Changes that an agent proposes open as a read-only Compare Files tab, and the agent keeps working while you read the diff.
• Studio also picks up changes made on disk, whether by an agent, another editor, Git, or the Terminal panel. The Explorer panel updates as files and folders change, the project reloads when its dependencies change in project.json, and open .xaml, .cs, and .txt files reload automatically. If a file has unsaved changes in Studio, you choose whether to keep your version or load the one on disk.

For details, refer to UiPath for Coding Agents, Coding Agents, and About Automation Projects.

Autopilot as a coding agent

Autopilot is the coding agent that comes with Studio. It loads UiPath skills as it needs them, so it can work on any type of UiPath project or task, such as building RPA workflows, agents, and Maestro flows, running platform operations, or troubleshooting. It has built-in tools, subagents, memory, and Model Context Protocol (MCP) integration. Open the Autopilot panel, or press Ctrl + Alt + I to focus it from anywhere in a project or solution. For details, refer to the Autopilot user guide and Coding Agents.

Source control and visual workflow diff

The Source Control panel covers the Git work of a project, from reviewing changes to recovering earlier work.

• The Changes section lists pending file changes with a diff for each file, and commits and pushes them. Generate commit message writes the commit message from your staged changes using Autopilot.
• The Graph section displays the commit history as a multi-lane graph, where you can check out a branch, revert a commit, or reset to it, and Stash Changes sets unfinished work aside until you need it.

For details, refer to The Source Control Panel.

Workflow comparisons show changes on the canvas. Sequences, flowcharts, and state machines, including the states nested inside a state machine, render side by side with additions, removals, and modifications highlighted, and selecting a modified activity shows a diff of its changed properties.

A Git conflict in a text file, such as a .cs coded workflow, a .json configuration file, or a .txt file, opens in a three-way merge view, with Local and Remote panes and an editable Result pane. For details, refer to Solving Conflicts.

Opening a project no longer reorders the references of its workflows. Previously, Studio rewrote and reordered the AssemblyReferences of a .xaml file when it opened the workflow, so opening a project left modified files in source control. Studio now keeps the existing references in their order, and saves a workflow on open only when it adds a missing required reference, namespace, or trigger argument.

Extensions

The Extensions panel lets your team add the tools it works with to Studio, such as file viewers, editor tools, and coding assistants.

• Recommended offers a curated set designed around RPA workflows, including Claude Code, OpenAI Codex, and the Low-Code Viewer.
• You can also browse the full Open VSX catalog, manage your Installed extensions, or install a Custom extension from a local .vsix file.
• When you open a file that Studio can't render natively, Studio offers to install the right extension for it.

Extension updates are manual by default. An extension card displays an Update button when a newer, compatible version is available, and Update all extensions, in the More actions menu of the panel header, updates all of them together.

A release delay holds back newly published extension versions, so that a faulty or compromised version can be removed from Open VSX before Studio installs it. It applies to every install and update, including automatic updates, and is 72 hours by default. You can change it from Release delay, in the same More actions menu. Newer versions are still offered after a warning. For details, refer to Release delay.

Administrators control what can be installed: a new Extensions category in Automation Ops policies and the governance file sets which extensions users can install, which publishers are trusted, and how extensions are updated, including a release delay that users can't change. For details, refer to The Extensions Panel and Extensions Settings.

The Low-Code Viewer (Preview) extension lets you follow a coded automation the way you follow a workflow. It renders coded (CodedWorkflow) C# automations as a visual canvas next to the source. For details, refer to Low-Code Viewer.

The Terminal panel

The Terminal panel runs command-line tools, including coding agents and the UiPath CLI, in the project or solution folder. Each terminal opens as a tab with its own shell, and you can choose PowerShell, Windows PowerShell, Command Prompt, Git Bash, or Windows Subsystem for Linux (WSL), depending on what's installed on your machine.

Several agents can work at the same time. A terminal running in the background shows a Working badge while it runs, and a Needs attention badge when a longer-running command finishes, a command fails, or it needs your input. Find searches the output of a terminal, and URLs and file paths in the output are links. For details, refer to The Terminal Panel.

Choose the Robots a project supports

Each project sets the oldest Robot version that can run it, so you can keep building for the Robots you run today and move projects to 26.10 as you upgrade them. The new Minimum Robot version setting, in the new project window under Show advanced options and in the Project Settings window, offers 22.4, 24.10, and 26.10. New projects default to 26.10, and for the built-in templates, the new project window remembers your last selection.

A lower version reaches older Robots, and Manage Packages tells you when a package has no version that supports it. Existing projects keep their current version until you change it. Changing the version reloads the project, and Robots older than the selected version can't run the published package. The setting isn't available for Windows - Legacy projects. For details, refer to Setting the Minimum Robot Version.

Build and publish solutions in Studio

In 2025.10, Studio could open, edit, and save solutions created in Studio Web. You can now take a solution from creation to publishing in Studio.

• You create one from Solution on the Start page, or with Create new solution when you create a new process or a project from a template.
• The Add to Solution menu in the Explorer panel is grouped into Maestro Orchestrate, Maestro Automate, and RPA sections, as in Studio Web, and the .flow canvas of Maestro projects is provided by the UiPath Maestro extension.
• You can browse all the projects in a solution, including apps, agents, API workflows, and agentic processes, and open their files in the built-in text editor.

For details, refer to Creating solutions in Studio and Creating a Maestro project.

You can debug a project that calls other projects of the solution. When the file you debug calls another project through Run Job, Studio deploys the sibling projects to a debug folder in your Personal Workspace, where they run as Orchestrator jobs. Breakpoints and stepping apply only to the project you debug. For details, refer to Debugging projects that call other projects.

The Publish Solution split button publishes every project of the solution together to the Orchestrator Tenant Feed, to the Orchestrator Personal Workspace Feed, where it's also deployed and activated, or to a local folder. Publish Active Project publishes only the project you're working in, and Publish Project, in the Explorer panel, publishes one project of the solution on its own. For details, refer to Publishing a single project.

Live authoring on unattended robots

You can build UI automations on the machine of an unattended robot. For Unattended Robot connections, the Remote Session Settings window has a Session Mode option.

• With Live authoring, the robot keeps one remote session for the whole connection, you indicate and record UI elements on the remote machine, and its screen is streamed in the Remote View panel.
• Remote run only keeps the previous behavior, with a separate Orchestrator job for every run or debug session.

The remote debugging target of an unattended robot is remembered per tenant and folder, and Configure Remote Debugging in the Debug ribbon tab is renamed to Configure Remote Session. For details, refer to Live authoring.

Apply Healing Agent suggestions in Studio

The target changes that Healing Agent suggests can be reviewed and applied to the project in Studio. Healing Agent data moved from the Autopilot panel to the new Observability panel, which you open from the right rail in projects that use the UI Automation activities package.

You can analyze the most recent healing data from Orchestrator or load a Healing Agent debug file, review the target change suggested for each affected activity, and apply it. For details, refer to The Observability Panel and Applying Healing Agent suggestions in Studio.

Deployment and administration

UiPath Platform Installer

Starting with 2026.10, Studio is installed and updated with the UiPath Platform Installer, together with the Robot and the other UiPath desktop clients. The UiPathStudio.msi installer is no longer provided. Install with UiPathPlatformLTS.26.10.msi or UiPathPlatformOffline.exe. The LTS installer follows the Enterprise LTS (26.10 line) channel, which receives 2026.10 patches. Automatic updates are off by default on this channel.

For machines without internet access, use the offline installer: a single EXE that includes the full 2026.10 package, with Studio, the other desktop clients, Delegate, and Cartographer. Studio 2025.10 and earlier keep receiving patches on UiPathStudio.msi until their end of support. For details, refer to Migrate from the classic MSI.

Studio Legacy, the StudioX Excel Addin, the SAP Solution Manager plugin, and the bundled activity packages are optional components that you select during installation. For details, refer to Install Studio.

A new official package feed

Official UiPath activity packages resolve through https://pkgs.uipath.com/official/index.json, replacing the Azure DevOps-hosted https://pkgs.dev.azure.com/uipath/Public.Feeds/_packaging/UiPath-Official/nuget/v3/index.json. Configurations that still point at the old address are rewritten to the new one on upgrade.

If your network restricts outbound traffic to an allowlist, add pkgs.uipath.com to it. Otherwise Manage Packages cannot list or install official packages.

Assembly signing

The DLL files that Studio generates during publishing and at design time can be code-signed, so that Windows Defender Application Control (WDAC) policies and other application control policies that allow only signed code can load them.

• Per project, the Certificate signing tab of the Publish Process window takes a certificate, its password, an optional timestamper, and a Sign assemblies option.
• Globally, Backstage View > Settings > Locations has the Default Publish Certificate, Dynamic DLLs Certificate, and Sign Tool Path settings, and Automation Ops policies can set these locations too.

For details, refer to Signing Assemblies.

Improvements

Performance improvements

• Studio starts and opens workflows faster.
• A skeleton loading state covers the canvas while a workflow opens, and the finished workflow appears in a single frame.
• Peak memory on a large just-in-time compile with multiple definitions is reduced roughly five-fold. Projects with tens of thousands of discarded package references no longer stall on a check that could run for up to half an hour.

Designer

• Double-clicking an Invoke Workflow File activity, also in a long running workflow, opens the invoked workflow.
• Double-clicking an activity that has no deeper level to open selects it and moves the focus to the Properties panel.
• When you select multiple activities, the context menu offers the options that support a multiple selection, such as Disable Activity, Surround with Try Catch, and Delete, and runs them on all the selected activities.
• Read-only property fields render grayed, but you can scroll them, select their text, and copy it.
• Activities nested deeper than the designer's nesting limit show a stand-in card that explains Maximum nesting level reached. Double-click the parent activity to view its contents.
• Undo and redo work while the focus is in the Properties panel, and undoing Change Type on an activity reverts it in one step.

Compact Design Experience

• The Compact Design Experience, introduced in 2025.10, puts more of each activity on the canvas. The primary property of an activity is displayed as a pill on its card, and selecting it opens the matching field in the Properties panel. Switch case values, Try Catch exception types, and Else If conditions are displayed as pills too. For details, refer to Compact Mode.
• Activities from packages such as Excel, Word, or Presentations show their primary property as a pill too, and activity cards are wider.
• Each container activity ends with an End row named after the activity, such as End If or End Sequence.
• Each branch of a Try Catch or Switch activity is a single container.
• A container activity no longer displays the header of the Sequence that makes up its body.
• The Else branch starts collapsed when you add an If activity, and Hide Else hides an empty Else branch. For details, refer to The If Activity.
• When the project uses Object Repository, a UI Automation card shows the descriptor name in a pill.

Activities

• The Invoke Code activity has a code editor on its card, with syntax highlighting and IntelliSense for C# and VB.NET, instead of a separate window. The same editor is available for Python script inputs. Requires the System activities package 26.6.1 or later.
• When you rename an argument of a workflow, Studio updates every Invoke Workflow File activity that references it and keeps the values already set in those invocations.
• The context menu of an activity offers Mark as Private and Mark as Public, which control whether its values appear in execution logs.
• When a Catch block of a Try Catch activity is selected, the Properties panel exposes its exception type as an editable property.
• Studio warns before you rename an argument or variable that an Object Repository activity uses.
• The arguments dictionary of the Invoke Workflow File activity has a search box.
• Invoke Workflow File validation reports all argument mismatches together, instead of stopping at the first one. An argument that differs only between In and In/Out is reported as a warning, and invoke activities that are commented out are not validated.

Panels and layout

• The Ribbon display options in the panel menu set how much space the ribbon takes: Compact moves the commands into the title bar, Minimal shows icons without labels and is the default, and Expanded shows icons with labels. For details, refer to Ribbon Display Options.
• You can open and close side panels, such as Explorer, Activities, or Properties, by selecting their icons. Profiling moved from the Debug ribbon tab to its own side panel.
• The Properties, Outline, and Profiling panels show an empty state when nothing is open.
• The Debug Settings menu lists the settings you turn on or off separately from one-time actions, and the Wizards menu groups event-based triggers under User Events.
• The default filters of the Explorer panel include the Other category.
• The line number gutter of the code editor widget is narrower.
• Project type icons match the icons used in Studio Web, and the tenant list is sorted alphabetically.

Explorer panel and files

• Text files smaller than 10 MB open in the Studio editor, which shares its syntax engine with the Invoke Code editor, with syntax highlighting for .py, .sql, .ps1, .java, and .js files, in addition to C#, VB, XML, and JSON.
• Workflow files show what's inside them: Sequence, Flowchart, Long Running Workflow, or State Machine, and other file types have their own icons too. For details, refer to File and Workflow Icons.
• In the Explorer panel, Open with... opens a file with its default application or with an application you pick, Copy Path copies the path of a file or folder, and file and folder names can be renamed inline.
• The Open File Location option in the Object Repository panel opens the location of the underlying selector or descriptor file on disk. For details, refer to Reusing objects and UI libraries.
• When you open a project or a solution that has a README file at its root, Studio opens the README, unless it restored your previous tabs. The Open README file toggle under Settings > Design > Save and Publish turns this off.

Output and error messages

• You can select and copy words, ranges, or individual messages in the Output panel.
• Workflow Compiler failures show the full underlying exception, including inner exceptions and the stack trace, as expandable details on the error in the Output panel.
• Expression compilation errors quote the expression that caused them.

Projects and dependencies

• Namespace errors are marked in the Explorer panel, and the Repair Dependency option in the context menu of the affected dependency fixes them.
• Some activity packages ship a runtime-only variant meant for the Robot, such as UiPath.UIAutomation.Activities.Runtime.Portable, and a project that references one loses design-time features such as UI Explorer. The Explorer panel warns you about such dependencies, and Auto-fix replaces each runtime-only package with its design-time equivalent. For details, refer to Runtime-only Packages.
• The Manage Packages window and the Templates tab match each word you type separately, in any order, and tolerate typos, when you search the Official feed, the templates feed, or a local folder feed. A package whose ID starts with the text you type is listed first, and Orchestrator feeds and nuget.org keep their own search. For details, refer to Installing Packages.
• The Build Project Workflow Analyzer option checks the project for compilation errors without running or publishing it, such as an Invoke Workflow File activity that references a deleted or renamed file. For details, refer to About Workflow Analyzer.
• Maestro .flow files can be run and debugged from the ribbon, and have their own icon in the Explorer panel.
• The ST-USG-014 - Package Restrictions Workflow Analyzer rule supports more than 250 characters, and the less than (<) and less than or equals (<=) symbols.
• Studio displays more specific messages when an Integration Service connection is unavailable.
• Template cards show a version drop-down, and their full description, creator, and last updated date on hover.

Solutions

• Studio keeps up to three projects of a solution loaded, so switching between them doesn't reload the project, and saves your changes when you switch away. The Fast solution project switching setting, under Settings > Design > Save and Publish, is on by default.
• The context menu of the solution or of a folder has an Add > Folder... option, and projects that you create or import from the context menu of a folder are added to that folder. For details, refer to Organizing projects into folders.
• Resources in the Defined Resources panel open in a Studio tab for editing. For details, refer to Editing a resource.
• Add > File..., Add > Folder..., and Open Project Folder are available for every project type in the Explorer panel.
• Opening a solution that contains exactly one RPA project activates that project. The active project can be removed from a solution with the same delete confirmation as any other project.

Autopilot

• The Ask Autopilot shortcut in the Designer panel opens the Autopilot panel, and Ctrl + Alt + I focuses the Autopilot panel from anywhere in a project or solution.
• Opening a project shows a What's new page about coding agents and Autopilot, once per content revision. The page is also available from Help.

Remote debugging

• The agent-ready timeout used when starting a remote debugging session is configurable, for machines where signing in takes longer. For details, refer to Remote Debugging.

Coded automations

• The UiPath.Coded.Workflow activity package has various improvements and bug fixes. Add its latest version to your projects.

Bug Fixes

Designer and canvas

• Activities added to a workflow were misplaced after using the scrollbar in some large projects.
• UI Automation activities sometimes displayed a broken designer when opened in a drilled-in view.
• Double-clicking a validation error for a Flow Decision activity focused the flowchart instead of the activity. The same happened for Workflow Analyzer results on activities with their default name.
• Ctrl + D and Ctrl + E moved the selection to another activity instead of disabling or enabling the selected one.
• Undo didn't restore the time part of a date and time field.
• Drilling down to a Multiple Assign variable using Find References navigated deeper than the referenced activity.
• When activity assemblies failed to load on project open, Studio could save UnresolvedActivity placeholders in XAML files.

Activities panel

• Searching the Activities panel returned Excel activities that didn't apply when the Group by category option was selected.
• The Recent section of the Activities panel showed activities that did not match the search query, and installed activities appeared under both Installed and Available.
• The cloud activities catalog offered an activity that the project already provided under Available, and selecting it upgraded the package.

Activity configuration

• Studio became unresponsive when adding some activities from the UI Automation package v24.10 or older that used a target indicator.
• Studio became unresponsive when configuring some activities from the Amazon Web Services package.
• The properties of some Integration Service activities were not visible in the Designer after selecting a valid connection.
• Adding a Read Range activity from the Google Workspace or Microsoft 365 packages caused Studio to reload it continuously.
• A Given name () is not valid message appeared when configuring a For Each File/Folder activity.
• The value of an argument set with the Expression Editor in an Import SAP BAPI activity was not saved in some Windows projects.

Flowchart, Switch, and trigger activities

• The connection of the False branch in a Flow Decision activity disappeared in some flowchart workflows.
• You could not edit previously configured Switch activities in some projects after upgrading from Studio 2024.10.
• Setting a case value directly on a Switch activity lost the focus while typing.
• All case values of a Switch activity were cleared after a debug error followed by a rerun.
• In a Switch activity with the System.Char expression type, adding a second case flagged both cases with a Value already exists error before any value was typed.
• Placing a Trigger Scope inside a Parallel activity, or using more than one Trigger Scope in a workflow, showed a validation error.
• Adding a trigger to a workflow that already had a trigger didn't add the new trigger's arguments. Studio also adds missing trigger arguments when you open the workflow.

Invoke Workflow File and Run Job

• Dragging a workflow onto the designer created an Invoke Workflow File activity whose path had doubled separators, so the invoked file failed to compile.
• Selecting Refresh Arguments in the Invoke Workflow File activity dialog deleted the argument values configured in the calling workflow.
• Selecting Refresh on the input arguments of a Run Job activity left the output types stale, so run or debug failed with errors such as BC30560 'X' is ambiguous in the namespace.
• When an activity's type argument changed, for example when Extract Document Data switched back to DictionaryData, the variables bound to its outputs kept their old type.

Expressions and Object Repository

• An error indicator in the expression editor could hide the text being edited.
• Intelligent code completion filter buttons overlapped the top suggestions in some Windows - Legacy projects.
• You could not assign a value of type System.Object to type System.String in the To property of the Assign activity.
• You could not rename existing Object Repository elements in some projects.
• Renaming an argument or variable referenced by an Object Repository activity left the activity pointing at the old name, causing an exception at runtime.

Email and database activities

• Minimizing an email activity showed a You must provide a value for Connection validation error that disappeared when the activity was expanded again.
• A BC30451: 'LocalResource' is not declared error occurred in some flowchart workflows when entering a VB expression in the Collection Builder of a Send Email activity.
• Two additional parameters appeared when consuming a library that contained a Get Newest Email activity with the Email folder option configured.
• The Execute Select Query Synchronously activity failed on Snowflake tables with lowercase or mixed-case names.

Data Manager

• You could not edit the default value of a global variable in the Data Manager, and a global variable's default value was not saved to globalVariables.json.
• ReadOnly variables appeared as constants in the Data Manager, and their default values could not be edited.
• The Arguments section of the Data Manager stopped refreshing after you switched to another workflow.
• Studio became unresponsive when creating a variable from the Plus button on a secondary screen.
• Create variables and arguments from JSON schemas could not be used when Studio ran in a language other than English.

Variables and arguments

• The default values of required input arguments set in Studio were ignored when running some processes in Orchestrator.
• Argument default values set to an expression were ignored when Studio read a workflow's arguments.
• Processes with TimeSpan input arguments sometimes failed to run from Orchestrator with an Invalid format for argument error.
• An Unable to cast object of type 'Microsoft.VisualBasic.Activities.VisualBasicValue' validation error occurred when setting the default value of a String argument in some StudioX projects.
• Arguments of a package published from StudioX were not displayed on the Orchestrator process registration page.

Explorer panel and solutions

• Deleting a folder whose files were selected in the Explorer panel caused Could not find file errors.
• Paste in the Explorer panel didn't copy files into an empty area unless an item was selected, and stayed disabled after you copied a workflow.
• Copying a solution to Git could create infinitely nested folders.
• In solution projects, the resource picker listed only the first 100 assets, and its search didn't find the others.

Opening and loading projects

• Not all dependency nodes were loaded when opening some projects with several custom libraries with nested dependencies.
• Changes to project names made in the Project Settings window were not reflected in the Open Recent list.
• Studio could not open some projects on slower machines, because internal requests timed out before the project finished loading.
• Studio could stop responding while opening a medium or large project, with the progress message stuck on Adding dependencies....
• Studio could freeze while loading a project after a rendering error in the busy indicator.
• The System.Activities.Statements and System.Activities.Expressions namespaces appeared as unresolved in some projects.
• Machine resource consumption increased in some projects after upgrading from a previous Studio version.
• The first time you opened a project in a Studio session, activity packages couldn't read the project settings while they loaded, so some packages saved wrong default values to the project's .settings folder.

Windows - Legacy projects

• Studio Legacy often failed to open projects, and a second Legacy instance could start for a project that one was already hosting.
• You could not access Studio settings from Windows - Legacy projects.
• Converting a Windows - Legacy project to Windows could resolve dependencies below the version the project requires, producing NU1605 build errors.
• A BC30311: Value of type 'SecureString' cannot be converted to 'CvString' error occurred when converting Windows - Legacy projects that contained a CV Type Into activity.

Templates and new projects

• The Catch block that assigned the System Exception transition in the Initialization state did not work in some projects created from the Robotic Enterprise Framework template.
• In a localized Studio, the Project Notebook of a new Task project was always created in English.
• When you started a project from an Automation Hub idea and changed the language or target framework, the Automation Hub URL was lost. The Automation Hub URL was also not saved when publishing some projects.

Compilation

• Unexpected compilation errors occurred in some projects that contained a large number of test cases.
• A VB project that also contained .cs coded workflows reported C# parse errors, such as CS1525 and CS1002, against valid files.
• In a project that contained only coded workflows, the generated CodedWorkflow.cs file referenced a WorkflowRunnerService that was not generated.
• Projects containing activities from the UiPath.OmniPage.Activities package failed validation.
• Ambiguous-argument errors in the UiPath.IntelligentOCR.Activities namespace occurred in some projects that contained the Extract Document Data activity.
• Argument 'Value': BC30560 and CS0433 errors occurred in projects with libraries that contained Search Using SOQL activities.
• When developing a project in a shared folder, a Could not load file error sometimes occurred when running or publishing projects that contained multiple libraries.

Command line

• Publishing projects with coded workflows from the command line failed with The project has validation errors and cannot be published.
• Building a project that used UiPath.IntelligentOCR.Activities from the command line failed with a version error.
• Building from the command line left generated files locked after validation.

Workflow Analyzer

• Publishing a library sometimes failed with an InvalidOperationException from the ST-USG-026 Activity Restrictions rule, which could also under-report violations.
• The ST-MRD-004 - Unreachable Activities rule was triggered in projects with long running workflows.
• The ST-NMG-004 - Display Name Duplication rule was triggered after updating the System activity package from v23.4.3 to v24.10.7.
• In the Workflow Analyzer settings, coded workflow rules showed Missing translation as their scope.

Publishing

• Publish as Test Case failed with compilation errors after workflows were moved or their folders renamed.
• Both design and runtime packages were created when publishing some libraries with Separate Runtime Dependencies disabled, and the Project Dependencies Mass Update Tool referenced runtime packages regardless of this setting.
• The Project Dependencies Mass Update Tool failed with an Access Denied error in projects connected to TFS.
• Packing or publishing into an output folder inside the project directory bundled the previous package into the new one. Studio rejects such an output path.
• Bindings were generated for assets that were part of non-publishable files.
• The Publish window was missing the Tenant and Personal Workspace options until Studio restarted, and didn't list the tenant feeds when you had no Orchestrator folder.
• Publishing to the Personal Workspace Feed failed when StudioX was licensed with an Automation Express license.

Debugging and running

• An Unable to start execution error occurred in some projects with libraries when debugging was paused at a breakpoint.
• Stop Execution windows appeared while debugging when Studio marked files as modified on open.
• Restarting a debugging session reused the previous compilation, so edits made while execution was paused did not run.
• Run and Debug could fail with Cannot find or create LiteDb database because the project's reference database was deleted while another client was still using it.
• Jobs started from Studio sent no folder key to the Robot, so activities saw an empty FolderKey and FolderKeyPath.
• Run in Picture-in-Picture ran Windows - Legacy processes in the main session instead of the isolated one.
• You could not troubleshoot workflows with a Testing Robot license.

Source control

• A System.NullReferenceException error occurred when switching Git branches with uncommitted changes.
• A No error message appeared when resolving merge conflicts.
• Solving Git conflicts in projects with Excel files could corrupt those files.
• The Studio message box did not indicate that Undo does not apply to unversioned files.
• Show History on a project didn't work after you checked in a deleted file.
• Cloning or pushing over HTTPS to a GitHub Enterprise Managed Users organization failed before Studio asked for your credentials.

Governance

• Activities restricted by the Activities to hide Automation Ops setting could still be used in some projects.
• Studio could not apply an Automation Ops policy when the organization display name contained non-ASCII characters.
• Manage Sources restrictions in an Automation Ops policy were ignored when the policy had no default package sources.
• Adding a package source that used %userprofile% through an Automation Ops policy created a duplicate feed.

Orchestrator and authentication

• Changing the tenant could fail silently while Assistant had a job running or Autopilot for Everyone was enabled.
• Transient Orchestrator disconnections cleared the folder context, causing asset lookup failures and missing feeds.
• Authenticating to an on-premises Orchestrator with client credentials produced a token without the tenant, so API calls failed.
• With an Orchestrator that has pre-signed URLs disabled, transferring files through storage buckets, for example when you started a remote debugging session, failed with a 400 SharedAccessSignatureFailure error.
• The Browse for Types option could not be used when System.Management.Automation assemblies were blocked by group policies.
• An Evinced.SDK.Exceptions.EvincedSDKException: Authorization ERROR: Invalid token format error occurred in coded workflows that used the Evinced Selenium C# SDK for offline authentication.

User interface

• Closing an editor with Cancel or Esc could move the focus to another application.
• Studio could stop responding when switching the focus between open files.
• A corrupted Autopilot suggestions file caused errors whenever you selected an activity or focused an expression.

Security updates

• The bundled .NET runtimes were updated to .NET 10.0.14 and .NET 8.0.33 to address reported security vulnerabilities.
• The bundled OpenSSL library (libcrypto-3-x64.dll) was updated to 3.6.5 to address reported security vulnerabilities.
• System.Security.Cryptography.Pkcs was updated to 8.0.2 to address CVE-2026-84008 and CVE-2026-70162.
• System.Security.Cryptography.Xml was updated to 8.0.5 to address CVE-2026-96222, CVE-2026-96958, CVE-2026-96959, and CVE-2026-96960.
• The uv and Node.js runtimes bundled for the UiPath CLI were updated to uv 0.13.6 and Node.js 24.22.2, to address CVE-2026-111497 and to stop trusting the compromised eMudhra certificate authorities.
• The dotnet-svcutil tool, and the vulnerable System.Security.Cryptography.Xml and NuGet.Protocol versions it carried, are no longer shipped with Studio.

Removed Features

• The legacy Autopilot panel, with its Fix error, UiPath documentation search, and Healing Agent cards, and the embedded Fix validation error and UiPath documentation search actions are removed, as is the 2025.10.16 option to switch back to that panel. Fixing errors and searching the UiPath documentation are available in the Autopilot chat, and Healing Agent data is in the new Observability panel.
• The Slim View for Collapsed Activities design setting is no longer available in Studio. It remains in Studio Legacy, which opens Windows - Legacy projects.
• The Quick Tutorial window that opened when Studio started is removed. The HideGettingStartedScreen governance setting that hid it applies only to Studio Legacy. The tutorial is still available from the Help tab.
• The ribbon's pin button, the Ctrl + F1 shortcut, and double-clicking a ribbon tab no longer change the ribbon display. Use the Ribbon display options instead.
• The UiPathStudio.msi installer is replaced by the UiPath Platform Installer.

Activity Package Versions

The following activity packages and versions are installed with Studio when you select Install Activities in the UiPath Platform Installer, and can be found in the OfficialPackages local feed.

Activity package	Version
UiPath.UIAutomation.Activities	v26.10.7
UiPath.System.Activities	v26.10.0
UiPath.Excel.Activities	v3.6.1
UiPath.Mail.Activities	v2.12.10
UiPath.Word.Activities	v2.6.1
UiPath.ComplexScenarios.Activities	v1.5.1
UiPath.Presentations.Activities	v2.6.1
UiPath.Testing.Activities	v25.10.3
UiPath.WebAPI.Activities	v2.5.2
UiPath.Form.Activities	v26.4.0
UiPath.Callout.Activities	v26.4.0
UiPath.DataService.Activities	v25.2.0
UiPath.DocumentUnderstanding.Activities	v3.3.0