Start-AIShell does not seem to respect side-by-side installations of Windows Terminal and Windows Terminal Preview

[mmseng]

Steps to reproduce

• Have Windows Terminal and Windows Terminal Preview both installed
• Launch Windows Terminal Preview
• Run Start-AIShell
• Ask the AI agent to generate some code
• Use /code post

Expected behavior

Running Start-AIShell in Windows Terminal Preview splits the current tab into 2 panes and all interactions stay within Windows Terminal Preview.

Actual behavior

Running Start-AIShell in the production version of Windows Terminal works as expected. The current terminal tab splits into 2 panes and /code post sends code to the original terminal pane.

Running Start-AIShell in Windows Terminal Preview launches a new instance of the production version of Windows Terminal with a fresh terminal tab, and spits that tab into two panes. Using /code post sends code to the original tab of the Windows Terminal Preview instance which ran Start-AIShell, and nothing is sent to the terminal pane of the production Windows Terminal instance tab. If you close the Windows Terminal Preview instance and then use /code post, this error is returned: ERROR: Both the client and server pipes may have been closed. Pipe connection status: client(True), server(False)..

Disclaimer

I have very little idea what I'm doing with AI Shell, so maybe I'm just doing something wrong, or need to install it a different/additional way in order to use it with Windows Terminal Preview.

Environment data

Windows 10 Enterprise 22H2 19045.5737 and Windows 10 Enterprise LTSC 21H2 19044.5737
PowerShell 7.5.0
Windows Terminal 1.22.10731.0
Windows Terminal Preview 1.23.10732.0
AI Shell 1.0.0-preview.3

>$psversiontable
Name                           Value
----                           -----
PSVersion                      7.5.0
PSEdition                      Core
GitCommitId                    7.5.0
OS                             Microsoft Windows 10.0.19044
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1
WSManStackVersion              3.0

[daxian-dbw]

@mmseng Thanks for reporting this issue! It turns out to be a Windows Terminal issue and I've opened microsoft/terminal#18815 to track it.