Codex “thread not found”: Troubleshooting and a Recovery Case
Codex can show “thread not found” even when conversation history is still readable. Diagrams explain the difference between saved history and a conversation loaded for execution, followed by logs from a Windows case where sending recovered after reloading. Work through reopening, restarting, and checking a short response, then review read-only investigation and handoff options if the problem persists. Public counterexamples show why no universal fix can be claimed, and we have not verified a specific release that resolves the problem.