A fix for this issue will be available in version 2026.3.0 (upcoming release)
Implemented

AI Tools auto-formatter bug

avatar

PSU: 2026.2.5

If you have AiTools in a module and then you add a new tool via the GUI, PSU adds ALL the tools into the new, local AiTools.ps1. So the new file has all the tools from the module AiTools.ps1 + the just generated tool.

This reminds a bit of the buggy behaviour from read-only sections in earlier versions (4.x/5.x).

All Comments (4)

avatar

Hello @schubfre ,

Thank you for reporting this and for clearly describing the behavior you are seeing in PSU 2026.2.5.

Based on your description, the key point is that AI Tools supplied by a module appear to be written into the local `AiTools.ps1` file when a new AI Tool is created through the Admin Console, instead of only writing the newly created local tool.

We are going to reproduce this with a minimal module-based configuration and compare the state of `AiTools.ps1` before and after creating a new AI Tool through the GUI. We will also verify whether this only affects the serialized configuration file or whether it results in duplicated effective configuration after reload or restart.

For now, one detail would help us validate the same scenario: did the local `AiTools.ps1` file already exist before you created the new AI Tool, or was it generated for the first time by that action?

Best regards,
Ruben Tapia

avatar

Hi @rubentapia ,

the local AiTools.ps1 did not exist beforehand, it was created by adding a new AI Tool through the GUI.

Best Regards

avatar

@schubfre
Thank you for confirming that detail. That helps narrow down the scenario.

I’ll review and reproduce this behavior in my PSU 2026.2.5 lab environment, specifically checking what gets written to AiTools.ps1 when the file does not already exist and a new AI Tool is created through the GUI.

I’ll update the thread with my findings.

Best regards,
Ruben Tapia

avatar

Hey @schubfre

Thank you again for reporting this.

Our Development team has confirmed that this behavior is a bug and that it requires a code change. The fix is currently targeted for PSU 2026.3.0.

At this point, no additional troubleshooting is required from your side. We’ll keep the thread updated if there are any relevant changes.

Best regards,
Ruben Tapia

A fix for this issue will be available in version 2026.3.0 (upcoming release)