VSCode extension for PowerShell Universal, anybody using it?

Hello deroppi,

Thank you for confirming that the behavior persists with both the PowerShell Universal server and VS Code extension on version 2026.2.2.

Your earlier report covered the inability to edit Scripts and API endpoints. This update may extend the scope to App page management, particularly when a page remains on disk but is no longer visible or manageable through the extension. We will relate these findings to the previously reported issue and verify whether the App page behavior belongs to the same problem.

Could you please provide:

* The exact error or behavior when opening a Script or API endpoint and when adding a page.
* Whether the relevant actions are missing or appear but fail.
* The sanitized relative repository path and filename of the affected page.
* How that page was originally created.
* Whether Git Sync is enabled and, if so, whether it uses One-Way or Two-Way synchronization.

Please do not manually delete the affected page yet. The appropriate recovery method depends on the repository and Git Sync configuration.

Because this is a public forum, please sanitize all evidence before posting. Remove credentials, tokens, license keys, cookies, private keys, full connection strings, email addresses, usernames, customer data, tenant or account identifiers, internal domains, hostnames, IP addresses, and private URLs. Please do not upload unredacted HAR files, memory dumps, database backups, or complete configuration files to this public thread.

Best regards,
Ruben Tapia

I wrote that forum entry today, but it happened last week.
I meanwhile have recovered the page and switched back to the older extension.

Most pages most likely have been created through VScode with the old extension.
(I had other issues with creating pages through the web UI. The page would appear automatically in the menu, no matter what I did, and I could not remove it from being displayed. So I found, when creating via Vscode and extension I have no issues)

Git Sync is enabled, Two-Way. But I have to manually commit. Usually I control the changes and spilt into multiple commits, based on what has been changed.

The relative path for all pages is very simple. I don't use any special chars or blanks.
Typical would be a path like:
/dev/remotemtr
/common/netlookup

I will try to recreate that issue on the dev server.

I've used VS Code, the api endpoints are saved differantly on PSU it seems the extension can no longer edit them.

Hello deroppi and scheived,

Thank you both for the additional information, and please accept our apologies for the delays.

Please allow us some time to incorporate these scenarios into our lab testing this week. We will compare the behavior of resources created through VS Code and the Web UI, including the reported differences when editing endpoints and managing App pages.

We will provide an update once we have completed the initial validation.

Best regards,
Ruben Tapia

I wrote that forum entry today, but it happened last week.
I meanwhile have recovered the page and switched back to the older extension.

Most pages most likely have been created through VScode with the old extension.
(I had other issues with creating pages through the web UI. The page would appear automatically in the menu, no matter what I did, and I could not remove it from being displayed. So I found, when creating via Vscode and extension I have no issues)

Git Sync is enabled, Two-Way. But I have to manually commit. Usually I control the changes and spilt into multiple commits, based on what has been changed.

The relative path for all pages is very simple. I don't use any special chars or blanks.
Typical would be a path like:
/dev/remotemtr
/common/netlookup

I will try to recreate that issue on the dev server.

@deroppi @scheived

We have reproduced part of this but not all of it. There will be another update to this thread within the next 24 hours either way but if you could provide more information it could help:

1. Did the page disappear immediately after saving, or only after a refresh, restart, commit, or sync?
2. Was the page label gone entirely, or did it remain without the Edit pencil when the row was hovered?
3. Was the page still visible in the PSU Web UI?
4. How did you recover the page?

what is going on?
I was kind of happy meanwhile using the ironmansoftware.powershell-universal 2026.2.3

This morning vscode told me the extension is deprecated and I should "Migrate" to the Devolutions version.
So I tried, and got devolutionsinc.devolutions-powershell-universal 2026.1.1
And that version has the old 5.x look and feel again and is not any better.

So I installed the "deprecated" version again, that funny enough holds the highest version number.
code --install-extension ironmansoftware.powershell-universal

what is going on?
I was kind of happy meanwhile using the ironmansoftware.powershell-universal 2026.2.3

This morning vscode told me the extension is deprecated and I should "Migrate" to the Devolutions version.
So I tried, and got devolutionsinc.devolutions-powershell-universal 2026.1.1
And that version has the old 5.x look and feel again and is not any better.

So I installed the "deprecated" version again, that funny enough holds the highest version number.
code --install-extension ironmansoftware.powershell-universal

Sorry to hijack this support request but genuinely echoing @deroppi words here, what's going on here?

The extension to migrate to looks like it was last updated 6 months ago according to the marketplace and the new "Devolutions, Inc" publisher on the marketplace is unverified with just this extension.

Is this the genuine new extension and publisher or should we be avoiding this migration? There has not been any news of a migration ahead of time so this is out of the blue and highly suspicious.

what is going on?
I was kind of happy meanwhile using the ironmansoftware.powershell-universal 2026.2.3

This morning vscode told me the extension is deprecated and I should "Migrate" to the Devolutions version.
So I tried, and got devolutionsinc.devolutions-powershell-universal 2026.1.1
And that version has the old 5.x look and feel again and is not any better.

So I installed the "deprecated" version again, that funny enough holds the highest version number.
code --install-extension ironmansoftware.powershell-universal



Sorry to hijack this support request but genuinely echoing @deroppi words here, what's going on here?

The extension to migrate to looks like it was last updated 6 months ago according to the marketplace and the new "Devolutions, Inc" publisher on the marketplace is unverified with just this extension.

Is this the genuine new extension and publisher or should we be avoiding this migration? There has not been any news of a migration ahead of time so this is out of the blue and highly suspicious.

@Michael Taylor and @deroppi

I will help to find out what's going on. The Devolutions PowerShell Universal marketplace entry is legitimate. But it appears that maybe the cut-over occurred prematurely or out-of-step. In the meantime, my advice for immediate relief is to download and install manually as needed the VSIX file. They can still be downloaded by way of URLs like:

https://marketplace.visualstudio.com/_apis/public/gallery/publishers/ironmansoftware/vsextensions/powershell-universal/5.6.2/vspackage

https://marketplace.visualstudio.com/_apis/public/gallery/publishers/ironmansoftware/vsextensions/powershell-universal/2026.2.3/vspackage

@deroppi - The update on the original issue you reported is still forthcoming. I appreciate your patience.

Hello all,

The Devolutions PowerShell Universal 2026.2.3 extension has been published and is the new, official extension for PowerShell Universal. The Ironman Software extension is correctly deprecated.

Some Background

We originally requested deprecated from the Microsoft Visual Studio Marketplace team in February 2026. After the request, we published the Devolutions PowerShell Universal extension 2026.1.1. The original intent was to leave the Ironman Software version as-is and publish a new PSU extension under the new organization as an entirely new extension.

The MS Marketplace team did not deprecate our extension and, after publishing the Devolutions extension, it was flagged as impersonation and removed from the store. In order to publish the new extension, we had to upload it to the Ironman Software organization. We've been trying to get the other extension deprecated since then. It finally happened sometime last night, which directed users to the originally published 2026.1.1 Devolutions extension. First thing this morning, we were able to publish the 2026.2.3 version of the extension. This is the exact same extension as Ironman Software PSU 2026.2.3 under a new organization.

We were unaware you would not be able to install previous versions of the PSU extension once the deprecation took place. Thanks @DataTraveler for providing the workaround for the direct download to the old VS Code packages.

Overall, the deprecation process has been a struggle and we've let Microsoft know our feedback on the process.

Moving Forward

I understand there are some issues with the new extension that require resolution on our end to ensure it works as good and, eventually, better than the previous extension. I do want to highlight the extension relies heavily on features of the server so upgrading just the extension may not fix all extension behavior. The extension is now part of the core of the product so any feedback, bug reports and feature requests fall into the same backlog so continue to let us know what you need and what is not working.

While the Devolutions PowerShell Universal 2026.2.3 extension seems to work fine in VS Code (a little slow, but it works okay), I'm wondering if it's possible to make its file access provider available to other VS Code extensions, such as Cline.
Right now, although I can edit and save files directly to PSU using the extension, other extensions don't have access to those files.
As development shifts more toward AI-driven "vibe coding," an extension that lacks AI agent file access becomes far less useful for complex tasks. I’m not sure if this is technically feasible given VS Code's architecture, but without this feature, the PSU extension's usability might be limited to acting as a simple editor—something that risks becoming obsolete in the near future.

what is going on?
I was kind of happy meanwhile using the ironmansoftware.powershell-universal 2026.2.3

This morning vscode told me the extension is deprecated and I should "Migrate" to the Devolutions version.
So I tried, and got devolutionsinc.devolutions-powershell-universal 2026.1.1
And that version has the old 5.x look and feel again and is not any better.

So I installed the "deprecated" version again, that funny enough holds the highest version number.
code --install-extension ironmansoftware.powershell-universal



Sorry to hijack this support request but genuinely echoing @deroppi words here, what's going on here?

The extension to migrate to looks like it was last updated 6 months ago according to the marketplace and the new "Devolutions, Inc" publisher on the marketplace is unverified with just this extension.

Is this the genuine new extension and publisher or should we be avoiding this migration? There has not been any news of a migration ahead of time so this is out of the blue and highly suspicious.

@Michael Taylor and @deroppi

I will help to find out what's going on. The Devolutions PowerShell Universal marketplace entry is legitimate. But it appears that maybe the cut-over occurred prematurely or out-of-step. In the meantime, my advice for immediate relief is to download and install manually as needed the VSIX file. They can still be downloaded by way of URLs like:

https://marketplace.visualstudio.com/_apis/public/gallery/publishers/ironmansoftware/vsextensions/powershell-universal/5.6.2/vspackage

https://marketplace.visualstudio.com/_apis/public/gallery/publishers/ironmansoftware/vsextensions/powershell-universal/2026.2.3/vspackage

@deroppi - The update on the original issue you reported is still forthcoming. I appreciate your patience.

@deroppi - We finally have progress on this. I have submitted bug reproduction steps upstream. I will update this thread again next week to confirm but I would expect the bugs you have found to be fixed in a subsequent release of PSU. Thank you for reporting this and for your patience. We're not finished quite yet but these bugs will be in the rearview mirror soon.

@krisr

PSU 2026.3.0 will expose the file editing features of the extension as an MCP server so that agents will be able to use it directly, even outside of VS Code.

Sorry,
vscode showed me I should update to:
Identifier devolutionsinc.devolutions-powershell-universal
Version 2026.2.4

I installed and it again has the old interface known from v5

I will go back to
Identifier ironmansoftware.powershell-universal
Version 2026.2.3
as that version works somehow.

@deroppi

The orphaned page bug has been reproduced and reported upstream 👍. I believe that this and the endpoint issue will be fixed in a subsequent release. I was not able to reproduce the error with script editing. Let's review again when 2026.3.0 is released to see if anything else remains.