August 2026 release notes for Studio.

Build number: 2026.0.199

UiPath's official activity packages now 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. Existing installations are migrated on upgrade — configurations still pointing at the old address are rewritten to the new one, so there's nothing to change on your end.

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

Opening a workflow meant watching the canvas assemble itself. Activities appeared in batches as the viewport populated, property widgets filled in afterwards, and a large file visibly put itself together piece by piece before it settled.

A skeleton loading state now covers the design surface while that work runs, and the finished workflow appears in a single frame once the layout goes quiet. The time it takes to open a file is unchanged — what's gone is the flicker of half-drawn intermediate states. If another panel keeps the layout busy, the canvas is revealed anyway rather than leaving the placeholder up. Connectors in virtualized sequences also no longer show a phantom down arrow while the canvas is populating.

Studio ran a reference cleanup pass every time it opened a workflow, which rewrote and reordered the AssemblyReferences in the .xaml file. Opening a project just to look at it was enough to leave modified files behind in source control. That cleanup no longer runs on open, so your workflow files stay byte-for-byte as they were.

Peak memory on a large multi-definition just-in-time compile is down roughly five-fold. Projects carrying tens of thousands of discarded package references also no longer stall on a check that could run for up to half an hour.

The ribbon has supported three display states for a while, but there was no single place to pick between them — a plain Ribbon on/off toggle in the panel menu, the ribbon's own pin button, Ctrl+F1, and double-clicking a tab all changed ribbon state independently.

The panel menu, opened from the layout icon, now has a Ribbon display section above Default panels listing three options that behave as a single-select group:

Selecting a state applies it immediately, with no reload, and your choice persists across sessions. Reset layout returns the ribbon to Minimal, the default. The picker replaces the old Ribbon toggle, the pin button, and the Ctrl+F1 and tab double-click gestures, so ribbon state is now controlled from a single place.

When a coding agent proposed changes to your workflows or code, the comparison opened in a separate window, and the agent sat blocked until you closed it.

Those comparisons now open as a read-only Compare Files tab alongside your other documents, and the agent carries on working while you read the diff at your own pace. Paths relative to the project folder are resolved correctly.

The Explorer panel gave a distinctive icon only to .xaml files, and every .xaml file got the same one. Everything else — project files, documents, scripts, notes — rendered with a generic blank document icon, so telling files apart meant reading filenames.

Workflows now show what's inside them: Sequence, Flowchart, Long Running Workflow, or State Machine, each with distinct variants for entry points, files with errors, and files excluded from the project. The same icons appear in the New File menu, so what you pick is what you see in the tree.

Other file types get their own icons too: .cs, .vb, .json, .xml, .md, .txt, .js, .pdf, .doc, .docx, .xls, .xlsx, .xlsm, .bpmn, .dmn, and .uiproj.

Some activity packages ship a runtime-only variant meant for the Robot rather than for authoring, such as UiPath.UIAutomation.Activities.Runtime.Portable. A botched publish or upgrade can leave a project referencing one, and because those variants carry no design-time components, features like UiExplorer and the selector editor stop working with nothing in the interface explaining why.

The Explorer panel now shows a warning when it detects such a dependency: Runtime-only packages detected. Auto-fix to restore design-time features. Auto-fix swaps each runtime-only package for its design-time equivalent. If one can't be replaced — because of a version conflict, for instance — Studio names the packages that need a look and points you to Manage Packages to resolve them by hand.

Marking a property widget read-only disabled everything about it: the scrollbar was dead, the text couldn't be selected by dragging or double-clicking, and there was no way to copy the value out. Fields such as Preview, which exist to be read, were the ones it hurt most.

Read-only fields now render grayed to show they can't be edited, while staying interactive in every other respect — you can scroll them, select their text, and copy it, and hovering or focusing no longer lights the field up as though it were editable. This applies on the canvas, in a locked designer, and in diff mode. Opening the advanced editor on a read-only property shows the expression in a selectable read-only view rather than a locked editor. Editing itself is still blocked.

The Low-Code Viewer is part of the Recommended group in the Extensions panel, alongside Claude Code and OpenAI Codex, and installs from there in one click.

Build number: 2026.0.198

Studio's integrated terminal was a single, basic shell: one session at a time, no choice of which shell it ran, and no way to search its output or keep track of what was running in it. Anything beyond a quick command meant switching to an external terminal, and coding agents started a broken, non-persistent session because they detected themselves as running nested inside another agent.

The terminal is now a full multi-session panel built for command-line work inside Studio.

New terminal opens terminals as tabs that you create, rename, duplicate, and close independently. Each tab is fully isolated, with its own shell process, output, and scrollback, and new terminals start in the current project folder.

Select a different shell to open lists the shells installed on your machine, so you choose one per terminal instead of being locked to a single shell. On Windows, the list covers:

On macOS, it lists your configured shells. Extensions that run commands get their own tab, grouped under Extensions.

Keystrokes now reach the running program: the arrow keys navigate command history and move the cursor, and Shift+Enter enters multi-line input. Output renders in full color, so modern command-line interfaces (CLIs) and full-screen text applications display correctly.

Any CLI tool or coding agent runs as a clean, top-level session with full history, persistence, and resume — the same as if you had launched it from a standalone terminal.

Studio could install extensions from the marketplace but gave you no way to see or change the settings an extension exposes, so reconfiguring one meant editing files by hand.

Each extension's details page now has a Settings tab listing every setting the extension contributes, each rendered with the control that fits its type:

The tab also provides a Search settings box, inline validation, and Reset Setting and Reset All actions. Edit in settings.json opens the underlying file when you need to work with it directly.

The Scope selector controls where a value is written:

Values are read back through the standard configuration API, so extensions pick up changes immediately without a restart. A More actions (⋯) menu on each extension card and an action bar on the details page expose the same per-extension actions as the panel, including Extension Settings.

Double-clicking an activity that contains another level of the workflow opens that level, but double-clicking one with nothing to open did nothing at all. Double-clicking a node that has no deeper level now selects it and moves focus to the Properties panel, so you can start editing straight away. The behavior is consistent across designers, including nodes in flowcharts and long-running workflows.