Octopus Deploy, a deployment automation tool, has historically used the Runspace classes to host PowerShell scripts within its Tentacle process, resulting in some compatibility issues and frequent bug reports when scripts that work in PowerShell.exe fail under Tentacle. To address these challenges, Octopus decided to switch to a simpler and more reliable model from version 1.4 onwards, which involves directly invoking PowerShell.exe and piping results, thus ensuring greater compatibility and reducing complexity. Although initially considering multiple invocation modes to support backward compatibility, the decision was made to phase out the existing in-memory model, with a temporary option to revert to it through a special variable, and fully transition users to the new model in future releases. This change reflects Octopus's commitment to leveraging standard platforms like PowerShell to avoid "lock-in" strategies, aligning with their founding philosophy to build on open technologies.