i really don’t see the need to impose limitations on workflow and slow people down by stopping .psjs from being able to launch and run other scripts.
The whole purpose is to speed up workflow, there is no authority such as adobe marketplace overseeing when a .psjs script is released on the internet to see if there is anything malicious in it. So why stop it from launching another .psjs script.
I have a .jsx script launcher which i find greatly improves my efficiency as its lined to a keyboard shortcut, i can then run up to 5 listed ‘last run’ scripts and point it to multiple folders as well as have several buttons to launch more permanent script. I’d like to be able to use more modern scripting and not rely on scriptUI anymore but with all these limitations in both .psjs and UXP as a whole you’re stopping people making the switch.
Please just allow running of .jsx and .psjs from UXP and from other .psjs scripts for the sakes of efficiency and workflow, keeping things as they are for ‘security concerns’ is just slowing adoption.
People are handing over their entire systems to claude to control, or downloading enormous LLMs from questionable sources. I don’t think they really care if PS can run a line of malicious code from a secondary script they may have picked to run which they could run as a primary script from the browse menu anyway