After using wsl mode codexapp doesn't load the window correctly

What version of the Codex App are you using (From “About Codex” dialog)?

26.305.950

What subscription do you have?

Free

What platform is your computer?

Win11

What issue are you seeing?

After using wsl mode codexapp doesn't load the window correctly and gets stuck in the background this is the console log

PS C:\Users\tiddler\Desktop> allowDebugMenu=false allowDevtools=false allowInspectElement=false buildFlavor=prod enable
[wsl] eligible distro list listResult="NAME STATE VERSION\n* Ubuntu-24.04 Running 2\n docker-desktop Stopped 2"SL
Launching app agentRunId=null allowDebugMenu=false allowDevtools=false allowInspectElement=false buildFlavor=prod enableSparkle=false nodeEnv=undefined packaged=true platform=win32iscovered SSH alias stderr=""
[spawn-async] Spawning process inside WSLfailed to resolve discovered SSH alias stderr=""
[spawn-async] Spawning process inside WSL: url.parse() behavior is not standardized and prone to errors that have secu
[discover-ssh-config-remote-connections] failed to resolve discovered SSH alias stderr=""vulnerabilities.
[discover-ssh-config-remote-connections] failed to resolve discovered SSH alias stderr=""
(node:52268) [DEP0169] DeprecationWarning: url.parse() behavior is not standardized and prone to errors that have security implications. Use the WHATWG URL API instead. CVEs are not issued for url.parse() vulnerabilities.
(Use Codex --trace-deprecation ... to show where the warning was created)izing client
[spawn-async] Spawning process inside WSLg app-server transport
[IpcRouter] I am the routern] Starting app-server connection hostId=local transport=stdio
[electron-message-handler] Statsig: waiting for auth context before initializing clientxt=connecting previous=disconnect
[ElectronAppServerConnection] Initializing app-server transport
[ElectronAppServerConnection] Starting app-server connection hostId=local transport=stdio
[ElectronAppServerConnection] Codex app-server connection state changed hostId=local next=connecting previous=disconnected transport=stdio

What steps can reproduce the bug?

open wsl

What is the expected behavior?

_No response_

Additional information

_No response_