I’m working on Windows PC applications - such as game development - using Codex as an extension to VS Code (or Cursor, etc.) and the docs for the Codex extension state:
Windows support is experimental. For the best Windows experience, use Codex in a WSL workspace
Though then we’re also essentially developing a Linux app and Windows PC tooling can have issues with the files on the virtual Linux drive. All the friction moves to the Windows development tooling.
I am thinking to try to use the VS extension without WSL and just adding a bunch of Linux style command line apps to mimic Linux like behavior so that at least reduces some Codex friction. Maybe even combine this with an agent skill windows-cli-map such as Use rg instead of grep, etc.
Anyone have any best/better practices for using Codex to target Windows PC builds?
Here’s hoping for Codex/OpenAI native Windows tooling in the near future.
I have since tried this - got Codex to recommend a bunch of Windows CLI equivalents / replacements for 'nix style CLI apps and made their recommended use into a skill. Seems to work great!
Following up on your question: at the moment, the best option is to publish the skill in a GitHub repository. This allows others to install it directly using the GitHub URL, for example: