Make local config path configurable instead of fixed to ~/.codex/config.toml

[imjb87]

The VS Code Codex extension currently hard-codes the local config path to ~/.codex/config.toml, which causes issues in environments where the user’s home directory isn’t writable or is locked down (e.g., remote SSH containers, shared hosting, Cloudways-style environments, corporate setups, restricted $HOME permissions, etc.).

It would be helpful if the extension allowed the config path to be overridden, similar to how you can set a home path for remote SSH containers to get around permissions issues.

This would make the extension far more flexible and usable in real-world environments where $HOME can’t be modified.

Happy to discuss implementation approaches. Let me know your thoughts.

[etraut-openai]

Thanks for the suggestion. This is the discussion forum, which is for questions and help. If you'd like to propose a feature or behavioral change, please open an enhancement request in the issue tracker. We generally prioritize features based on upvotes (thumbs-up reactions) from the community.