openai / openai/codex

Chat Logs not appearing

Open
#46,465 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

app app-server bug Linux
Dominant language
Rust
Stars
125k
Forks
19.4k
PR merge metrics
PR metrics pending

Description

What version of the Codex App are you using (From “About Codex” dialog)?

Linux Version 26.908.61612

What subscription do you have?

Max 20x

What platform is your computer?

]Linux 7.0.0-31-generic x86_64 x86_64

What issue are you seeing?

Support report: active Codex task opens with blank conversation pane

Prepared: 2026-09-18. Draft only; not submitted.

Environment

  • Installed Linux package: chatgpt 26.908.61612.
  • Ubuntu 24.04.5 LTS, Linux/X11 (from process metadata).
  • Affected task: SDIY WORK.
  • Task ID: 01a0a0af-bf27-7461-9f70-1c1a35953e7b.
  • Task created September 14; continued across multiple days.
  • Another task, Manager, remains readable.

Reproduction and impact

  1. Open the pinned SDIY WORK task in the desktop app.
  2. The conversation pane is blank; no messages load.
  3. Navigating directly to the task using the app navigation tool reports success but does not restore the messages.

The user cannot review the running task's conversation. The task continues executing and receiving user messages.

Verified observations

  • App task listing identifies SDIY WORK as active and pinned.
  • Task-reading tool returns current and completed turns with empty items arrays, even with includeOutputs=true.
  • A completed turn (01a0b599-710a-75c0-8025-64ff1fd3a25d) was returned with status=completed and items=[].
  • The original on-disk session transcript contains assistant commentary and final messages, including messages at 2026-09-18T17:57:25Z and later. Transcript reads remain successful.
  • The transcript measured 680,760,485 bytes during the latest check; an earlier check measured 664,352,689 bytes.
  • Logs show successful thread/read, thread/turns/list and thread/items/list routing with errorCode=null.
  • Repeated renderer global errors were recorded around attempts to view the conversation:
    "ResizeObserver loop completed with undelivered notifications."
    Examples: 2026-09-18T16:32:16.697Z, 16:32:56.892Z, 16:33:08.111Z.
  • The original task and history have not been edited, truncated, archived, forked or deleted.
  • No app restart or cache reset has been performed during this diagnosis because the task is actively running tests and implementation work.
  • A separate Markdown snapshot of recent assistant messages was created as a reading workaround; it does not repair the original conversation view.

Unconfirmed hypotheses

History loading/pagination, message reconstruction, or renderer layout failure may be involved. The unusually large transcript may contribute. Neither transcript size nor ResizeObserver errors establish the root cause. The task-reading tool could have its own projection issue, so empty item lists alone do not prove the native app uses the same failing path.

Requested investigation

  • Inspect native conversation loading and item pagination for this task ID.
  • Explain why completed turns return empty item lists despite stored message records.
  • Check handling of large, long-running goal transcripts and rendering errors.
  • Recommend a recovery procedure that preserves active execution, worktree changes, and the full original history.

Sharing limits

This report contains diagnostic metadata only. Full session transcripts, repository contents, tokens, and complete app logs are not attached. Any request for additional logs should specify the minimum relevant subset so it can be reviewed before sharing.

What steps can reproduce the bug?

Feedback ID: 019ffc90-bc25-7f62-8fdd-3fdfdcf078c0

What is the expected behavior?

Chat should appear, when clicking on chat it does not appear

Additional information

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing native conversation loading and item pagination for task 01a0a0af-bf27-7461-9f70-1c1a35953e7b. Compare thread/read, thread/turns/list, and thread/items/list with the stored transcript, and inspect the recorded renderer errors. Done means identifying why items are empty and providing a recovery path that preserves active execution and history.

Written by the indexing model from the issue text.

Assessment

Tech stack
linux, rust
Domain
desktop
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.