app-server: retain thread listener across disconnects#12373
Merged
Conversation
Keep the per-thread listener alive when the last client unsubscribes or disconnects so listener-side active turn history survives reconnects and running thread/resume can merge an in-progress turn snapshot. Add targeted ThreadStateManager regressions for listener retention on disconnect/unsubscribe and explicit teardown cleanup on thread removal. Co-authored-by: Codex <noreply@openai.com>
celia-oai
approved these changes
Feb 22, 2026
…stener # Conflicts: # codex-rs/app-server/src/codex_message_processor.rs
Update the Bazel module lockfile after `rules_rs` crate extension facts drifted, so `just bazel-lock-check` passes again. Co-authored-by: Codex <noreply@openai.com>
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
thread/resumecan merge an in-progress turn snapshot after reconnectThreadStateManagerregressions for disconnect/unsubscribe retention and explicit thread teardown cleanupAdded unit tests, and I manually tested to confirm the fix