codex - 💡(How to fix) Fix Custom pets fail to load in WSL environments due to path normalization [2 comments, 3 participants]

Custom Pets do not load correctly when running Codex from a WSL-enabled environment.

TL;DR

Normalizing the custom pet asset path to consistently point to the expected \pets directory may resolve the issue with Custom Pets not loading in WSL-enabled environments.

Guidance

• Verify that the custom pet directory path is correctly configured and accessible from both the Windows host and WSL environment.
• Check if the path normalization issue can be mitigated by using a consistent path separator (e.g., forward slash /) in the custom pet configuration.
• Investigate if the Codex environment provides any built-in path normalization functions or utilities that can be used to translate Windows paths to WSL-compatible paths.
• Test loading Custom Pets with a simplified path configuration to isolate if the issue is specific to complex paths or the normalization process.

Example

No specific code example can be provided without more details on the Codex configuration and custom pet asset loading mechanism.

Notes

The solution may depend on the specific version of Codex and WSL being used, as well as the configuration of the custom pet assets. Further debugging may be required to identify the exact cause of the path normalization issue.

Recommendation

Apply a workaround by manually normalizing the custom pet asset paths to ensure consistency between the Windows host and WSL environment, as the root cause of the issue appears to be related to path normalization.