By NODVIEW editors

Sources

Codex after a provider switch: readable history is not a resumed chat

What Codex CLI 0.167.0 changes for saved chats: history access, provider admission errors and an unsent continuation draft rather than guaranteed session portability.

Changing a model provider and resuming a saved chat are different operations. In the Codex CLI 0.167.0 release, OpenAI says saved chats remain visible after a provider switch. If the server will not resume a session, users can read its history and prepare a continuation in a new chat. This does not promise that the original session can run with any replacement provider.

The repository change description separates history discovery from permission to run. Resume lookup includes different providers, while fork lookup keeps its provider filter. The released code distinguishes a provider mismatch, missing configuration and an organization's required provider. Read the reason for refusal first: making history visible does not remove configuration or access requirements.

When continuation is available, the interface offers c to continue in a new chat; in the released notice code, that shortcut is conditional. The PR describes the resulting text as an editable, unsent draft. A saved draft example in the repository refers to the previous conversation by name. That reference alone does not establish that another provider receives the full transcript. Before sending, inspect the draft, current provider and information actually needed for the next step.

Check recovery with three separate questions: was the right history found, can it be read, and does the new chat have enough context for the specific task? Add a brief objective, accepted decision and next action if the draft lacks them. NODVIEW compared the release notes, PR, source files and test examples at tag 0.167.0; we did not install the CLI, switch providers or run those tests. This account concerns the reviewed terminal-client version, not every desktop-app release.