fix: keep session lists user-facing - #511
Closed
epodivilov wants to merge 1 commit into
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What
Why
Codex stores top-level conversations and internal worker threads together. Exposing the raw store through ACP makes internal sessions appear resumable and leaks transport context into session titles.
How
The list request continues to restrict provider source kinds, then applies defensive filtering using thread metadata. Title cleanup stays provider-local and reads history only for untitled rows whose preview contains no usable text after context removal.
Refs: ACP-290
Verification
npm run typechecknpm testnpm run buildNot verified
npm run test:e2e: this environment has neitherCODEX_API_KEYnorOPENAI_API_KEY.