Codex Desktop macOS: Archived Conversations page corrupts/blank overlay after scrolling
What version of the Codex App are you using (From “About Codex” dialog)?
Codex Desktop App: 26.608.12217, build 3722
Bundled Codex CLI:
codex-cli 0.138.0-alpha.7
What subscription do you have?
No response
What platform is your computer?
macOS 26.4.1 build 25E253, Apple Silicon / arm64
What issue are you seeing?
The Settings -> Archived Conversations / 已归档对话 page becomes visually corrupted after scrolling a few times. It looks like a renderer/layout/virtualized-list failure rather than a normal app exit.
Observed behavior from a 16-second local recording:
- Open Codex Desktop.
- Go to Settings.
- Open Archived Conversations / 已归档对话.
- Two-finger scroll / swipe a few times.
- The archived conversations list area turns into a large pale red / blank block.
- The overlay then expands/covers the main content area and part of the left settings sidebar.
- The UI does not recover in that view; restarting Codex is currently the reliable workaround.
This is distinct from opening a long conversation and scrolling inside the chat transcript. The repro surface here is the archived conversations browser under Settings.
Related but not identical: #27168 reports blank rendering while scrolling long conversations. This issue is specifically about Archived Conversations page scrolling on macOS.
What steps can reproduce the bug?
- Launch Codex Desktop on macOS.
- Open Settings.
- Click Archived Conversations / 已归档对话 in the left settings sidebar.
- Scroll the archived conversations page/list a few times.
- Observe the page becoming blank/corrupted with a large pale overlay.
What is the expected behavior?
The archived conversations page should remain stable while scrolling, including when there are no visible archived items or when the list is empty/loading.
Additional information
Local checks after the repro:
- No matching macOS
~/Library/Logs/DiagnosticReportsnative.crashreport was created at the repro time. - No fresh Crashpad
.dmpappeared at the repro time. - Codex main process and renderer processes were still running after the visual corruption.
- Unified logs did not show a clear
render-process-goneor native crash signal during the repro window. - App logs under
~/Library/Logs/com.openai.codex/2026/06/11/continued to show normal request routing around the same time; no obvious fatal renderer crash appeared.
This suggests the app is not necessarily exiting; the visible failure looks more like renderer/compositor/layout state corruption in the archived conversations settings page.
I have a short local video recording of the repro, but I am not attaching it publicly because it contains local UI/account context. I can share a redacted recording or targeted logs if useful.
3 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
Additional repro/diagnostic note:
I tried the lightweight recovery path again:
Cmd+Rdoes not recover the corrupted Archived Conversations view.This seems like a useful signal that the underlying archived thread data is probably still fine and that the failure is in the page's render/layout state. Updating the search input appears to force the archived conversations list to re-filter/re-render/re-measure, which clears the blank/pale overlay. A normal app-level refresh shortcut does not appear to invalidate the same state.
So the bug may be closer to virtualized-list measurement/cache invalidation or compositor/layout state in the Archived Conversations page than to data loading or a native crash.
Closing as duplicate of #27362. I added the extra recovery/diagnostic note there:
Cmd+Rdoes not recover the Archived chats view, but typing in the search field forces the page/list to re-render and clears the overlay.