Build number: 2026.0.197

Debugging a file that calls into another project used to mean deploying that other project to Orchestrator yourself before you could even start — publish it, save the solution to the cloud, and only then hit Debug.

Now, debugging a file that calls into another project via Run Job resolves those cross-project calls automatically: Studio deploys the sibling projects to a debug folder in your Personal Workspace, where they run as Orchestrator jobs whenever they're invoked, with no manual Save Solution to Cloud step and no setup before you hit Debug.

Studio only provisions the sibling projects when it actually needs to — if it can tell that the file you're debugging never reaches a Run Job call, provisioning is skipped entirely and debugging starts right away. Breakpoints and stepping stay in the project you're debugging; the invoked projects run remotely and aren't stepped into.

Publishing a solution used to mean publishing each project inside the solution one at a time. A new Publish Solution split button in the ribbon replaces that experience with a single wizard that packages every project in the solution together. The wizard allows you to set the package name, version, description, and release notes once and choose where it goes:

If you only need to publish one project rather than the whole solution, the same split button's menu also offers Publish Active Project and Publish Active Test Cases, both of which skip the wizard and only publish the project you're working in. Outside solutions, the Publish button keeps working exactly as it did before.

Right-clicking a single activity has always brought up its full context menu (Disable, Surround with Try Catch, and more), but selecting multiple activities at once collapsed that down to a stripped-down menu with only a limited set of actions. Multi-selection now gets the same full menu as a single activity, and every action that applies runs against your entire selection instead of just the first activity you clicked.

Studio's file editor used to render only a handful of file types (C#, VB, XML, and JSON), with syntax highlighting, while everything else opened as plain text. The file editor now shares the same syntax engine as the Invoke Code editor, so .py, .sql, .ps1, .java, and .js files get full syntax highlighting too.

Build number: 2026.0.196

You can now read an extension's documentation before and after installing, and Studio will tell you when a newer version is available.

Selecting an extension in the panel opens a details tab with its README: description, feature list, configuration options, and screenshots. This offers more information about the extension and removes the need to search it in a different application.

When a newer, compatible version of an installed extension is available, its card displays an Update button. The search filters @updates and @outdated list every extension with a pending update, and Update All in the panel header updates them together.

Auto-update is off by default, so extensions only change when you choose to update them. It can be enabled globally or per extension. After an update completes, the card shows a Reload option to restart the extension and load the new version.

You can install a specific version of an extension or download it as a .vsix file for offline installation, both from the context menu on each card.

Reviewing workflow changes is now visual by default. Instead of a raw XAML diff, comparisons render the workflow the way it was built: sequences, flowcharts, and state machines shown side by side, with additions, removals, and modifications highlighted directly on the canvas.

Selecting a modified activity opens the properties panel with a diff of its modified properties, so you can see exactly what changed rather than just that something changed. The diff opens in a regular editor tab instead of a modal, so you can keep working in Studio while reviewing it. Studio remembers your preferred view, visual or text, across sessions.

The Invoke Code activity now embeds an ActiPro-powered code editor directly on the activity card, replacing the previous plain-text preview. The editor provides syntax highlighting and IntelliSense for C# and VB.NET, so you can write and edit code inline without opening a separate editor window.

Requires System activities package 26.6.1 or later.

Log messages in the Output panel are now selectable text. You can select words, ranges, or individual messages and copy them, just as you would in a terminal.

The context menu offers a Copy option for just the message and a Copy (JSON format) option for the structured log data, so there's no need to manually clean up double-escaped paths.

The Explorer panel's default active filters now include the Other category, so items that don't fall into a standard category are visible without extra setup.