Consider CustomExecution over ShellExecution

[sourishkrout]

There's a chance it might simplify the initializing of a task and provide access to stdout (if required). There's also a chance it might just work as a wrapper for inline-execution.

From the VS Code API:

    /**
     * Class used to execute an extension callback as a task.
     */
    export class CustomExecution {
        /**
         * Constructs a CustomExecution task object. The callback will be executed when the task is run, at which point the
         * extension should return the Pseudoterminal it will "run in". The task should wait to do further execution until
         * {@link Pseudoterminal.open} is called. Task cancellation should be handled using
         * {@link Pseudoterminal.close}. When the task is complete fire
         * {@link Pseudoterminal.onDidClose}.
         * @param callback The callback that will be called when the task is started by a user. Any ${} style variables that
         * were in the task definition will be resolved and passed into the callback as `resolvedDefinition`.
         */
        constructor(callback: (resolvedDefinition: TaskDefinition) => Thenable<Pseudoterminal>);
    }

[sourishkrout]

Here's a PoC implementation: https://github.com/stateful/vscode-runme/blob/main/src/extension/terminal.ts

[sourishkrout]

Limited access and control over stdin through to the Pseudoterminal interface. Not actionable beyond PoC.