Environment inheritance and/or predefined variables in newly created tabs

[sikr]

With plain old Command Prompt (cmd.exe), when I set an environment variable and start a new Command Prompt from within the initial one via cmd.exe, this environment variable is also present in the newly created Command Prompt. I can also combine cmd.exe with start to create a new window and the environment variable is available there.

I can't figure out how to achieve this in Windows Terminal creating a new tab using wt.exe nt. Also I wasn't able to find a possibility to predefine environment variables e. g. in Profiles. I can't believe I'm the only one missing this so may be I'm just missing something...

Example

Start cmd.exe and execute the commands prefixed with >

> set foo=bar
> echo %foo%
bar
> cmd
:: a new instance of cmd.exe is invoked in the current window
> echo %foo%
bar

Combined with start to create a new windows from the initial one:

> set foo=bar
> start cmd
:: a new instance of cmd.exe is invoked in a new window
> echo %foo%
bar

Similar "workflow" in Windows Terminal:

> set foo=bar
> echo %foo%
bar
> wt.exe new-tab
:: a new tab is created
> echo %foo%
Environment variable foo not defined

[sikr]

Looks like this is somehow related to:
Feature Request: Terminal should listen for the WM_SETTINGCHANGE for environment variable updates
and
Environment not inherited by new instances/tabs of windows terminal