VS Code: Codex entry in Copilot "Local" chat dropdown silently no-ops (command not found), root cause AbsolutePathBuf deserialization failure — reproducible with WSL mode both on and off

What version of the IDE extension are you using?

26.715.31925

What subscription do you have?

Plus

Which IDE are you using?

VS Code

What platform is your computer?

OS Version string: Microsoft Windows NT 10.0.26200.0 x64 Product name: Windows 10 Pro (EditionID: Professional) Display version: 25H2 Build: 26200.8655 Architecture: x64

What issue are you seeing?

This is the same underlying defect reported in #30436 and #29454 (Windows path
sent where a POSIX-anchored AbsolutePathBuf with an explicit base is
required), but the user-visible symptom here is different: instead of a
visible "Error creating task" toast, the panel/command simply appears to do
nothing at all, which makes the root cause much harder for end users to
self-diagnose.

What steps can reproduce the bug?

What steps can reproduce the bug?

1. Open any local folder as a VS Code workspace on Windows.
2. Sign in to Codex (ChatGPT Plus account), confirm codex doctor passes.
3. Toggle chatgpt.runCodexInWindowsSubsystemForLinux to true, reload VS

Code, click "Codex" in the Local dropdown → no-op, same AbsolutePathBuf
errors in Codex.log.

1. Toggle the same setting to false, reload VS Code, click "Codex" again →

identical no-op and identical AbsolutePathBuf errors in Codex.log.

1. Both native and WSL execution modes fail identically, confirming the WSL

toggle is not a variable in this defect.

What is the expected behavior?

What is the expected behavior?

Clicking Codex in the Local dropdown should open a working Codex session, or
at minimum surface a visible, actionable error to the user instead of a silent
no-op.

Additional information

Additional information

• Related/likely same root cause: #30436, #29454, #16815, #30373, #31983,

#32474.

• Full reproduction log available on request (Codex.log excerpts across

multiple activations, both WSL-mode and native-mode, all showing the
identical AbsolutePathBuf deserialized without a base path error).

• Workarounds attempted without success: toggling WSL mode both ways,

clearing ~/.codex/.tmp/plugins cache, re-authenticating via WSL-side
codex login, reinstalling/reloading the extension.