codex - 💡(How to fix) Fix Feature Request: Per-project agent environment configuration in Codex Desktop [2 comments, 2 participants]

What variant of Codex are you using?

Codex Desktop

What feature would you like to see?

Add support for configuring each project with its own agent environment (instead of the current global agent settings), so that within the same Codex Desktop instance:

• Project A can use one agent environment (e.g., Windows native)
• Project B can use a different agent environment (e.g., WSL)

This enables mixed development scenarios within the same Codex Desktop, removing current limitations where all projects must share the same agent context. This would be particularly valuable for teams or users who work on projects spanning different OSs, interpreters, or toolchains, and need contextual separation for model, skills, or execution settings per project.

This proposal is not a duplicate of any enhancement issues currently listed, and is focused on enabling mixed agent environments at the project level, enhancing developer productivity for heterogeneous setups.

Additional information

Current limitation: In the same Codex Desktop instance, you cannot have Project A use Windows native agent and Project B use WSL agent settings, limiting truly mixed development workflows. This proposal is intended to enable having separate, project-scoped agent environments compared to the existing global configuration.

(If needed, more details/examples can be provided.)