Issue Station
Sign In
Tools hereToolbox

codex - 💡(How to fix) Fix Codex Desktop pet tray omits active threads and shows inconsistent thread status

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…

Root Cause

The pet becomes unreliable as a "what is still running / waiting / ready" surface. In this case it hid a likely active/recent non-final thread while showing another thread with comparable local state.

RAW_BUFFERClick to expand / collapse

Environment

  • Codex Desktop: 26.519.41501
  • Platform: macOS
  • Pet: BSOD
  • Observed: 2026-05-24 around 06:26-06:32 UTC / 10:26-10:32 Asia/Dubai

Expected

The pet tray should reflect the same active/recent in-flight threads as Codex Desktop's local thread/session state, and statuses should be consistent across comparable threads.

Actual

The pet tray showed only two thread cards:

  • Thread A: current diagnostics thread
  • Thread C: a routing task thread

But local Codex state showed three fresh, non-archived, non-final threads:

  • Thread A: current diagnostics thread, updated 06:31:58 UTC, visible in pet
  • Thread B: profile-menu task thread, updated 06:31:56 UTC, missing from pet
  • Thread C: routing task thread, updated 06:31:39 UTC, visible in pet

Thread B was missing from the pet tray even though it was updated at almost the same time as Thread C.

At the screenshot time window, Thread B and Thread C had very similar session state:

  • latest assistant phase: commentary
  • latest event: token_count
  • no final_answer
  • no task_complete

So the pet tray appears to apply inconsistent filtering: one unfinished/recent thread is shown, another similar unfinished/recent thread is hidden.

Local evidence

~/.codex/state_5.sqlite showed the three newest non-archived threads updated within ~20 seconds of each other.

~/.codex/sessions/2026/05/24/*.jsonl showed:

  • completed older thread: final_answer / task_complete, correctly absent from pet
  • Thread C: commentary / token_count, visible in pet
  • Thread B: commentary / token_count, missing from pet
  • Thread A: visible in pet

Desktop logs also showed the missing Thread B conversation was created and registered as a browser sidebar thread:

  • created at 06:16:03 UTC
  • registered at 06:16:03 UTC
  • continued receiving route/session events around 06:30-06:32 UTC

Why this matters

The pet becomes unreliable as a "what is still running / waiting / ready" surface. In this case it hid a likely active/recent non-final thread while showing another thread with comparable local state.

Related but not identical

  • #22112
  • #22625
  • #21348
  • #12321

This does not look like the external CLI case: the affected threads are local Codex Desktop/App threads, and the mismatch is between the pet tray and local Codex thread/session state.

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…

Still need to ship something?

×6

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

Back to top recommendations

TRENDING

codex - 💡(How to fix) Fix Codex Desktop pet tray omits active threads and shows inconsistent thread status