Skip to content

fix(workbench): page visible conversation history first - #6908

Merged
M4n5ter merged 1 commit into
rust-previewfrom
codex/visible-history-pagination
Nov 14, 2026
Merged

M4n5ter merged 1 commit into
rust-previewfrom
codex/visible-history-pagination

Conversation

@M4n5ter

@M4n5ter M4n5ter commented Nov 14, 2026

Copy link
Copy Markdown
Member

Summary

Scrolling back through a long conversation used to read the tool and activity records inside collapsed turns before reaching earlier messages. The desktop chat now pages visible history for completed native-model turns. Each collapsed turn shows activity counts and recent image previews. Opening it loads the activity on demand. Steering messages and context checkpoints stay in chronological order.

Verification

  • Replayed a long conversation from a local copy of its history. The previous context checkpoint was in the first page of the new chat view, compared with 109 pages in the full transcript view.
  • Passed the relevant macOS desktop, tool-history, and paging tests, plus contract and formatting checks.

The screenshots below come from the same conversation reopened in the macOS desktop test renderer against a fixture Host. The first frame shows the collapsed turn and its final reply. The second shows the original activity after expanding the turn.

Reopened conversation with activity collapsed

The same conversation after expanding the activity

AI use

  • Generative tooling made a substantive contribution

Tool and scope: OpenAI Codex implemented and tested the change.

Checklist

  • Tests cover the change and fail without it
  • Format, typecheck and the affected suites pass locally

Does this PR entail a change in behavior?

  • Yes

@M4n5ter
M4n5ter merged commit 47f38d0 into rust-preview Nov 14, 2026
9 checks passed
@M4n5ter
M4n5ter deleted the codex/visible-history-pagination branch November 14, 2026 13: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