codex resume --all picker omits a session that can be resumed by ID

Summary

codex resume --all does not show an existing session in the picker, but codex resume <SESSION_ID> successfully resumes it.

Environment

• codex-cli: 0.87.0
• OS: Ubuntu 24.04.1 (Linux 6.14.0-37-generic x86_64)

Session details

• Session ID (resumable by ID): 019bc371-82cf-7d82-ad0b-96d026aaca73
• Session file exists at:

~/.codex/sessions/2026/01/15/rollout-2026-01-15T15-55-54-019bc371-82cf-7d82-ad0b-96d026aaca73.jsonl

• First line is session_meta with payload.id=019bc371-82cf-7d82-ad0b-96d026aaca73 and payload.cwd=/media/im3/plus/lab4/re_news/herenews-app.

Steps to reproduce

1. Run codex resume --all
2. In the picker, search/scroll for 019bc371-82cf-7d82-ad0b-96d026aaca73
3. Observe the session is missing
4. Run codex resume 019bc371-82cf-7d82-ad0b-96d026aaca73
5. Observe it resumes successfully

Expected behavior

The session should appear in the codex resume --all picker list.

Actual behavior

The session is omitted from the picker list but can be resumed by ID.

Potentially related observation

The session file appears to contain multiple session_meta lines for different payload.id values (not just the filename’s session ID). Example: grepping for "type":"session_meta" in the file returns multiple matches on different lines with different payload.id values.

Logs (snippets)

~/.codex/log/codex-tui.log contains (line numbers may vary):

• Resuming rollout from "/home/im3/.codex/sessions/2026/01/15/rollout-2026-01-15T15-55-54-019bc371-82cf-7d82-ad0b-96d026aaca73.jsonl"
• Resumed rollout with ... items, thread ID: ... 019bc371-82cf-7d82-ad0b-96d026aaca73