Skip to content

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

Description

@imjb87

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requestextensionIssues related to the VS Code extension

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions