Frequent account switching sometimes causes the extension to fall back from configured settings to Default #17016

What version of the IDE extension are you using?

26.323.20928

What subscription do you have?

ChatGPT / Codex-enabled subscription

Which IDE are you using?

VS Code

What platform is your computer?

x64

What issue are you seeing?

When I switch accounts frequently, the Codex extension does not always continue using my configured settings consistently.

I have a config file where I define fixed Codex behavior, including some configuration and permission-related settings. Most of the time, after switching accounts, the extension returns to the values from that config file as expected. However, sometimes it falls back to the default behavior/settings instead.

This happens intermittently rather than on every switch, and I see it more often in the VS Code extension than in CLI usage.

The main problem is that the extension appears to lose or ignore the configured state after account switching, even though the config file itself has not changed.

What steps can reproduce the bug?

1. Configure Codex using a persistent config file with non-default settings (including permission-related settings).
2. Use the Codex extension in VS Code.
3. Sign in and switch between accounts multiple times.
4. Continue using the extension after each switch.
5. Observe that:
   • most of the time, the extension uses the configured values correctly
   • but sometimes it falls back to default behavior/settings instead of the configured ones

This is not fully deterministic, but it happens often enough during repeated account switching to be noticeable.

What is the expected behavior?

The extension should consistently respect the configured values in the config file, even after repeated account switching.

If account switching is expected to reset some runtime state, it should still either:

• reload the config file correctly every time, or
• clearly indicate which settings are being reset and why

It should not silently fall back to default behavior when the config file still specifies non-default values.

Additional information

• This issue appears more frequently in the VS Code extension than in CLI usage.
• The config file itself is still present and unchanged when the problem happens.
• The issue seems related to account switching / account state transitions rather than the config content itself.
• I can provide sanitized config examples if needed.