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

What feature would you like to see?

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.

Additional information

_No response_