feat: annotate conversations with model_provider for filtering #5658
+469
−57
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Because conversations that use the Responses API can have encrypted reasoning messages, trying to resume a conversation with a different provider could lead to confusing "failed to decrypt" errors. (This is reproducible by starting a conversation using ChatGPT login and resuming it with API key login.)
Note this ended up making changes to
codex-rs/core/src/rollout/tests.rsbecause it had a number of cases where it expectedSomefor the value ofnext_cursor, but the list of rollouts was complete, so according to this docstring:codex/codex-rs/app-server-protocol/src/protocol.rs
Lines 334 to 337 in bcd64c7
If there are no more items to return, then
next_cursorshould beNone. This PR updates that logic.