Record realtime conversation history in Core - #41924
Merged
copyberry[bot] merged 1 commit intoAug 31, 2026
Merged
Conversation
## Why Realtime history should be recorded consistently for every Core host, including when no app-server event listener is attached. ## What changed - Move transcript segmentation, session boundaries, and backing-agent artifact promotion into Core for paginated threads. - Persist canonical realtime items through the thread store in event order and emit dedicated history lifecycle events for hosts to present. - Translate those Core events into the existing app-server realtime item notifications without app-server persisting the items a second time. ## Testing - Cover Core-only persistence across repeated sessions, ephemeral sessions, accepted and rejected steering, typed input ordering, and artifact promotion. - Verify app-server notifications correspond to the persisted timeline. GitOrigin-RevId: 7cbef14129d77f6d6d7099b733be91f5279c55f5
copyberry
Bot
force-pushed
the
copyberry/codex-internal-to-codex-oss/7cbef14129d77f6d6d7099b733be91f5279c55f5
branch
from
August 31, 2026 22:39
8833f2d to
64c9cde
Compare
copyberry
Bot
deleted the
copyberry/codex-internal-to-codex-oss/7cbef14129d77f6d6d7099b733be91f5279c55f5
branch
August 31, 2026 22:40
emarceloaguirre-hub
temporarily deployed
to
issue-triage
August 31, 2026 22:48 — with 
GitHub Actions
Inactive
emarceloaguirre-hub
temporarily deployed
to
issue-triage
August 31, 2026 22:48 — with
GitHub Actions
Inactive
emarceloaguirre-hub
temporarily deployed
to
issue-triage
August 31, 2026 22:48 — with
GitHub Actions
Inactive
emarceloaguirre-hub
temporarily deployed
to
issue-triage
August 31, 2026 22:49 — with
GitHub Actions
Inactive
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.
2 participants
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.
Record realtime conversation history in Core
Why
Realtime history should be recorded consistently for every Core host, including
when no app-server event listener is attached.
What changed
promotion into Core for paginated threads.
emit dedicated history lifecycle events for hosts to present.
notifications without app-server persisting the items a second time.
Testing
accepted and rejected steering, typed input ordering, and artifact promotion.