Issue Station
Sign In
Tools hereToolbox

codex - 💡(How to fix) Fix Multiple sidebar bugs after workspace directory migration: "56 years ago" timestamps, missing threads, threads vanish on click (macOS) [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openai/codex#17317•Fetched 2026-04-11 06:17:55
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
0
Author
jjhuang2023jjhuang2023
Participants
github-actions[bot]github-actions[bot]jjhuang2023jjhuang2023
Timeline (top)
labeled ×2commented ×1cross-referenced ×1
RAW_BUFFERClick to expand / collapse

After migrating my workspace from a path containing Chinese characters to an all-English path, the Codex Desktop app exhibits three persistent bugs. The underlying data in state_5.sqlite is fully intact and correct — these are rendering/UI layer issues.

Platform: macOS Darwin 25.4.0 arm64, CLI 0.117.0-alpha.12

Bug 1: All threads display "56 年" (56 years ago) timestamp after restart

After app restart, ALL threads — including newly created ones — show "56 年" (56 years ago) as the relative timestamp. New threads display the correct time at creation, but revert to "56 年" after restart.

This is a Unix epoch (1970) display: 2026 − 1970 = 56 years.

The data is correct — state_5.sqlite timestamps are valid millisecond integers (e.g. 1775804549416 = 2026-04-10), and session_index.jsonl has correct ISO8601 timestamps. The bug is in the app's time rendering on restart.

Bug 2: Some workspaces show "无线程" (no threads) despite having data

The sidebar shows "无线程" for several workspaces, but sqlite has many threads for those exact CWDs:

WorkspaceThreads in sqlite (archived=0)Sidebar shows
bilibili-video-analysis14无线程
health2无线程
drafts30Only 2 visible
work-management34Partial

This appears to be the same truncation/pagination bug reported in #14370.

Bug 3: Threads disappear when clicked

Clicking on a thread in the sidebar causes it to vanish from the list. The thread data still exists in sqlite but is no longer rendered.

Additional: codex app-server continuously modifies sqlite

The codex app-server process (running via Cursor extension) continuously un-archives child threads that have been archived, undoing manual state corrections. It un-archives ~51 child threads within seconds.

Steps to reproduce

  1. Have a workspace with ~247 threads across multiple workspace roots
  2. Restart Codex Desktop app
  3. Observe: all timestamps show "56 年" instead of actual relative time
  4. Observe: some workspace folders show "无线程" despite having threads in sqlite
  5. Click on any thread → it may disappear from the sidebar

Expected behavior

  1. Timestamps should display correct relative time (e.g. "3 days ago")
  2. All workspace folders should list their threads matching sqlite data
  3. Clicking a thread should open it, not hide it

Environment details

  • 247 total threads in state_5.sqlite
  • 141 thread_spawn_edges (parent-child relationships intact)
  • All 247 rollout_path entries point to existing files on disk
  • All timestamps in DB are valid millisecond Unix timestamps
  • WAL has been checkpointed (WAL file is 0 bytes)

Related issues

  • #14370 — very similar sidebar truncation behavior (threads hidden despite existing in sqlite)
  • #16599 — thread history loss after restart, related WAL/persistence issue
  • #16989 — PR "Durably flush shutdown state" — partial fix that doesn't fully resolve these

extent analysis

TL;DR

The most likely fix involves addressing the timestamp rendering issue and the truncation/pagination bug in the Codex Desktop app, potentially by updating the app's time rendering logic and fixing the bug reported in #14370.

Guidance

  • Investigate the timestamp rendering logic in the Codex Desktop app to determine why it's displaying "56 年" (56 years ago) after restart, despite correct data in state_5.sqlite.
  • Review the code related to the bug reported in #14370, as the truncation/pagination issue seems to be the same, and apply any available fixes or workarounds.
  • Verify that the codex app-server process is not interfering with the app's rendering by temporarily stopping the process and observing the app's behavior.
  • Check the app's configuration and settings to ensure that there are no issues with the workspace roots or thread visibility settings.

Example

No code snippet is provided due to the lack of specific code details in the issue.

Notes

The issue seems to be related to the app's rendering and pagination logic, rather than the underlying data in state_5.sqlite. The codex app-server process may be contributing to the issue, but its exact role is unclear.

Recommendation

Apply workaround: temporarily stop the codex app-server process and apply any available fixes or workarounds for the bug reported in #14370, while the development team investigates and addresses the root cause of the issue.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

  1. Timestamps should display correct relative time (e.g. "3 days ago")
  2. All workspace folders should list their threads matching sqlite data
  3. Clicking a thread should open it, not hide it
#docker error#permission error#memory optimization#batch processing#GPU compatibility

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING