I’ve had the same issue. After checking the extension output, it was an issue with my .codex/config.toml file. In my case in particular, the ‘model provider’ configuration:
Removing this setting entirely, I disabled/re-enabled the extension globally, and it started working by using the default model provider.
To clarify with steps:
- View > Output > selected ‘codex’ from dropdown.
- Identified error in logging, with model-provider configuration.
- Amended (Windows)
%USERPROFILE%\.codex\config.tomlby removing model-provider setting. - Disabled extension globally
- Enabled extension globally
Given the way I resolved this particular issue, I feel it is likely an issue with particular configuration deprecations when the extension updates. If that’s the case, then there could at least be some-kind of warning or continuity. Particularly if updates will be continuing to proceed at the same rate.