Configuration Updates: Follow symlinks and replace source file when TUI makes config changes

[novasbc]

Today whenever codex updates the main config file ~/.codex/config.toml it creates a new file and then replaces it, forcing a new inode.

I prefer to symlink this file to a version controlled locations, sometimes sharing this between different built iterations of codex with different default home directories. Most important is version control, because I am set up to deploy my dev environment easily based on a deployment git repo (eventually also ansible).

Anyways, I've been using locally built codex with updates to follow the symlinks and replace the source file. Yeah, it gets a new inode there too, so one can't actually use a hard link, but its an OK compromise in my book.

Checking to see if there's specific reason why it wouldn't be a desirable feature. I understand why it does the current replace to make the update atomic, so I'm trying to retain atomicity with my specific changes.

Thoughts?

[novasbc]

P.S. I prefer not to symlink the entire config directory. I don't necessarily want to always have the other assets codex writes into this directory potentially shared with another instance (or like one of the many codex forks).

[etraut-openai]

Thanks for the suggestion. If you'd like to suggest a new feature or behavior change, it's best to create a feature request in the issue tracker for this project. That way, it will be tracked by the codex team and considered for prioritization. We generally prioritize features based on the upvotes (thumbs-up reactions) from the community.