Bug/Regression? Debugger terminal commands require Enter in attached process console

debug-4489.far.ps1 を使用して、VS Code を pwsh にアタッチし、test1 を呼び出して、VS Code のターミナルに $host を入力することで再現する。アタッチされたプロセスのコンソールとターミナル入力のフローを追跡する。アタッチされた pwsh コンソールで Enter を押さずに、$host が評価されてホストのプロパティを出力すれば完了とする。

Prerequisites

• I have written a descriptive issue title.
• I have searched all open and closed issues to ensure it has not already been reported.
• I have read the troubleshooting guide.
• I am sure this issue is with the extension itself and does not reproduce in a standalone PowerShell instance.
• I have verified that I am using the latest version of Visual Studio Code and the PowerShell extension.
• If this is a security issue, I have read the security issue reporting guidance.

Summary

Debugger terminal commands require Enter in attached process console.

PowerShell Version

Name                           Value
----                           -----
PSVersion                      7.5.4
PSEdition                      Core
GitCommitId                    7.5.4
OS                             Microsoft Windows 10.0.26200
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1
WSManStackVersion              3.0

Name             : Visual Studio Code Host
Version          : 2025.5.0
InstanceId       : d51c83ef-d689-470d-914b-04cfe94b45b9
UI               : System.Management.Automation.Internal.Host.InternalHostUserInterface
CurrentCulture   : en-GB
CurrentUICulture : en-US
PrivateData      : Microsoft.PowerShell.ConsoleHost+ConsoleColorProxy
DebuggerEnabled  : True
IsRunspacePushed : False
Runspace         : System.Management.Automation.Runspaces.LocalRunspace

Visual Studio Code Version

1.106.3
bf9252a2fb45be6893dd8870c0bf37e2e1766d61
x64

Extension Version

ms-vscode.powershell@2025.5.0

Steps to Reproduce

(1) Open pwsh console (or in my case an app hosting PowerShell Core).

(2) In VSCode, attach to this process for PowerShell debugging.

(3) In pwsh, invoke the attached script debug-4489.far.ps1 -- it sets some breakpoints for testing.
debug-4489.far.ps1.zip

(4) In pwsh, type and invoke test1 -- it breaks into VSCode debugger.

(5) In VSCode terminal type $host and hit Enter.

Expected result
VSCode evaluates the statement $host and prints the output (the host properties in this result).
It definitely used to work like this some versions ago.

Actual result
Nothing happens in the terminal until we go to the attached pwsh console and hit Enter there.
(Why? And how a user is supposed to know this?)