Moving from ~/.codex to ~/.code

[zemaj]

We've always supported using both ~/.codex and ~/.code as directories for data storage and config files.

This worked well - if you had already used Codex and switched to Code, your settings would move with you.

However we've diverged so far from Codex that we're now seeing issues in how Codex reads config files we write. The can cause Codex to not start depending on the settings you've used on Code if you switch between them.

We've now changed our home directory policy so that we read from both ~/.codex and ~/.code, but only write to ~/.code (so that changes we write won't stop Codex from running).

Most users will not notice this change as it's backwards compatible. If you do have issues starting Codex, you might see an error like

Error loading configuration: missing field notifications
in tui

If you see this, just remove your ~/.codex/config.toml (or just remove the tui = { theme ... line).

On the flip side, if you start Code and it's missing some of your config settings, you may have had both a ~/.code/config.toml and a ~/.codex/config.toml. In this case, Code would have been writing to your .codex directory, so just copy your ~/.codex/config.toml to ~/.code/config.toml.

Note that this change will still allow you to stay logged in if you login to Codex and switch to Code.

[ropl-btc]

hey @zemaj does this mean that code is aware of both config files at the same time? or will it chose either one?

for example if i have some mcps on the codex config file and some mcps on the code config file, will code combined both or how is it handled?