Skip to content

Conversation

@bolinfest
Copy link
Collaborator

@bolinfest bolinfest commented Oct 24, 2025

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.rs because it had a number of cases where it expected Some for the value of next_cursor, but the list of rollouts was complete, so according to this docstring:

/// Opaque cursor to pass to the next call to continue after the last item.
/// if None, there are no more items to return.
#[serde(skip_serializing_if = "Option::is_none")]
pub next_cursor: Option<String>,

If there are no more items to return, then next_cursor should be None. This PR updates that logic.

@bolinfest bolinfest force-pushed the pr5658 branch 2 times, most recently from f429512 to 88bc431 Compare October 25, 2025 15:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant