invoke_expression should auto-execute pipeline after console start/switch instead of returning "Pipeline NOT executed"

[doraemonkeys]

When invoke_expression is called and no ready console exists (or the active console switched), the tool starts/switches a console but returns early with:

Started new console PID#... Pipeline NOT executed - verify location and re-execute.

This forces the AI model to make a second identical call just to execute the command. In practice, the second call always sends the exact same parameters — the "verify location" step adds no value since the pipeline typically includes its own cd.

Expected behavior: invoke_expression should start/switch the console and then execute the pipeline in a single tool call, with console context info prepended to the result.

I have an implementation ready, could I submit another PR?

[yotsuda]

@doraemonkeys Thank you for the report and for offering to contribute!

This is intentional behavior. PowerShell.MCP maintains a persistent session — unlike stateless tools (e.g., Bash tool in Claude Code), the console preserves its current location across invoke_expression calls. Because of this, pipelines typically do not include cd / Set-Location and rely on the current directory being correct.

A different console may have a different current location. For example, the previous console may have been in C:\MyProject\src, while a fresh one starts in ~. Auto-executing the pipeline here is dangerous — commands like Remove-Item could silently target the wrong path.

The "verify location and re-execute" step ensures the AI model checks the actual working directory and adjusts before executing. It only occurs on console start/switch, not on every call.