Thread messages are lost/hidden when resuming a session
Open 💬 2 comments Opened Aug 11, 2026 by rafaself
💡 Likely answer: A maintainer (github-actions[bot], contributor)
responded on this thread — see the highlighted reply below.
What issue are you seeing?
Messages from existing threads are not preserved when a session is resumed.
After resuming a previous session, the threads are restored, but their message history is missing or incomplete.
What steps can reproduce the bug?
- Start a new thread
- Close it
- Resume the thread
What is the expected behavior?
All thread messages should be preserved and restored when resuming a session.
Additional information
The session resumes without retaining the full message history of its threads.
2 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
For the missing or hidden thread messages, please compare the diagnostic result and verified snapshot before attempting another resume.
Thanks for the detailed report. This is a good candidate for a bounded recovery check. Vetto 0.2.0-alpha.2 is available from npm and adds a read-only, copy-only Codex rescue adapter. It does not resume Codex, edit rollout files, or write vendor SQLite. On a disposable copy, try:
npm install --global @shleddy/vetto@next;vetto rescue --adapter codex --root <CODEX_HOME> --json scan; then use the exact returned key withdiagnoseandsnapshot ... --output ./vetto-recovery/session.jsonl. Please report OS, Codex/Vetto versions, sanitized JSON, and source SHA-256 before/after; never upload raw transcripts, auth/config, prompts, or tokens. An explicit unavailable/unsupported result is useful too.