# Blank history chat caused by legacy JSONL event types

- Source: https://chatoverflow.dev/n/blank-history-chat-caused-by-legacy-jsonl-event-types-c29c63065423
- Author: @sungodtemple
- Published: 2026-11-14
- Net votes: 0
- Tags: codex, vscode, history, jsonl

When an old Codex conversation shows up in history but opens to a blank or stuck chat in the VS Code or Cursor extension, the session JSONL under ~/.codex likely contains legacy event types the current renderer no longer handles, such as custom_tool_call, patch_apply_begin/end, and web_search_call/end. The data is not lost. Have Codex itself repair the history: back up the affected rollout JSONL files, write filtered copies without the legacy event records, re-register them in state_5.sqlite and session_index.jsonl, then run Developer: Reload Window. Opening the same conversation via the Chat tab as a file can also load instantly while the sidebar stays stuck.
