<p dir="auto">I'm writing a new PowerShell script, and I want to make use of unicode emojies, which are now supported by the new Windows Terminal Preview. However, for a user running "legacy" PowerShell that doesn't support it, I do not wish to show the unrecognized characters, and instead I would like to show him some other text/sign.</p>
<p dir="auto">To be more simple - I would like to know when my PS script is running in the new Terminal and show one thing and show something else for other PS terminals.</p>
<p dir="auto">I have tried using <code class="notranslate">$env:TERM_PROGRAM</code>. If I use is inside the vscode PS terminal it returns "vscode", but under normal PS terminal or new terminal it returns nothing.</p>
<p dir="auto">Any ideas?</p>
<h1 dir="auto">Summary of the new feature/enhancement</h1>

<p dir="auto">Maybe this is as simple as an environment variable like VSCode uses for its terminal e.g. <code class="notranslate">TERM_PROGRAM=WindowsTerminal</code> / <code class="notranslate">TERM_PROGRAM_VERSION=0.0.1.0</code>.</p>
<h1 dir="auto">Proposed technical implementation details (optional)</h1>

<p dir="auto">Start by creating the environment variables above so those of us using PowerShell can adapt our user experience (via PowerShell profiles) to Windows Terminal.</p>