Allow PowerShell or WSL execution environment to be selected per project and per chat

The payload names no files or tests. Start by locating project and chat persistence, environment selection, and Windows/WSL path-handling entry points; then trace restoration of chats, file-browser paths, attachments, and terminal settings. Done means per-project and per-chat environments remain distinct, paths translate correctly, and chats stay visible when environments switch.

What variant of Codex are you using?

App

What feature would you like to see?

Title: Support per-project and per-chat Windows/WSL environments with reliable path handling

I regularly use Codex on Windows 11 with both Windows-native and WSL-native projects:

• C:\platform-tools requires the Windows agent and PowerShell.
• /home/mike/repos/PortfolioWatch requires the WSL agent and an Ubuntu-22.04 terminal.

Currently, changing the Agent or Integrated Terminal between PowerShell and WSL behaves like a global setting. Switching environments can make existing chats appear to disappear, disrupt project grouping, break file and attachment links, and cause the file browser to resolve paths using the wrong environment.

For example, Codex can incorrectly reinterpret WSL paths as Windows paths and produce invalid hybrids such as C:\home\... or C:\mnt\....

These path forms need to remain distinct and be translated deliberately:

• Windows native: C:\platform-tools
• WSL native: /home/mike/repos/PortfolioWatch
• Windows access to WSL: \\wsl.localhost\Ubuntu-22.04\home\mike\repos\PortfolioWatch
• WSL access to Windows: /mnt/c/...

Please add:

1. A default execution environment for each saved project:

   • Windows/PowerShell
   • WSL, including distribution selection
   • Inherit global default

2. A per-chat environment override when creating or reopening a chat.

3. Independent configuration of:

   • Agent execution environment
   • Integrated terminal shell

4. Persistent environment identity for every chat, including its working directory and path format.

5. Correct Windows-to-WSL and WSL-to-Windows path translation for the file browser, attachments and clickable file links.

6. A consistent task list where chats remain visible regardless of the currently selected environment.

Expected behaviour:

• Opening C:\platform-tools automatically restores the Windows agent and PowerShell terminal.
• Opening /home/mike/repos/PortfolioWatch automatically restores the Ubuntu-22.04 WSL agent and terminal.
• Windows-native and WSL-native chats can remain open simultaneously.
• Switching chats does not require changing a global setting or restarting Codex.
• Changing the integrated terminal does not reinterpret the chat’s working directory.
• The file browser never constructs invalid hybrid paths.
• Existing file and attachment links continue working after switching between Windows and WSL chats.

This would make Codex substantially more reliable for Windows power users who work across both native Windows and WSL projects every day.

Additional information

No response