WSLENV var set in Windows 11 is not honored in Warp WSL shell

[Lotti]

Pre-submit Checks

• I have searched Warp bugs and there are no duplicates
• I have searched Warp known issues page and my issue is not there
• I have included the logs (optional, but helps expedite the bug fix). Log gathering intructions

Describe the bug

Warp terminal overwrites WSLENV environment variable value instead of merge Warp value with the one coming from Windows 11, when opening a WSL shell.
On Windows Powershell my WSLENV variable is respect and works perfectly.

To reproduce

I simply installed Warp and observed that is not taking the correct WSLENV var I set on Windows. More details in "Expected behaviour" section.

Expected behavior

My WSLENV defined at user level:

WSLENV=AZURE_DEVOPS_EXT_PAT/u

WSLENV set by Warp:

WSLENV=WARP_HONOR_PS1/u:WARP_USE_SSH_WRAPPER/u:WARP_SHELL_DEBUG_MODE/u:TERM_PROGRAM/u:WARP_IS_LOCAL_SHELL_SESSION/u:SSH_SOCKET_DIR/u:WARP_

Expected WSLENV set by Warp:

WSLENV=AZURE_DEVOPS_EXT_PAT/u:WARP_HONOR_PS1/u:WARP_USE_SSH_WRAPPER/u:WARP_SHELL_DEBUG_MODE/u:TERM_PROGRAM/u:WARP_IS_LOCAL_SHELL_SESSION/u:SSH_SOCKET_DIR/u:WARP_

Screenshots, videos, and logs

My WSLENV var

WSLENV set by Warp

Operating system (OS)

Windows

Operating system and version

Windows 11 with Debian 12 as WSL

Shell Version

both bash 5.2.15 and zsh 5.9

Current Warp version

v0.2025.03.26.08.10.stable_02

Regression

No, this bug or issue has existed throughout my experience using Warp

Recent working Warp date

N/A

Additional context

No response

Does this block you from using Warp daily?

Yes, this issue prevents me from using Warp daily.

Is this an issue only in Warp?

Yes, I confirmed that this only happens in Warp, not other terminals.

Warp Internal (ignore): linear-label:b9d78064-c89e-4973-b153-5178a31ee54e

None

[acarl005]

Oops we should merge these instead of over-writing