Long Codex task becomes permanently "Request blocked" after successful completion

Summary

A long-running Codex Desktop task completed successfully, but every subsequent follow-up in that task now fails with Request blocked. The same account and project can use other tasks normally.

Uploaded diagnostic thread: 019f4564-da0e-7a90-98c5-ab31f7fe149f

Timeline

• The task completed benign local research-app implementation and testing successfully at 2026-07-17 01:33 PT.
• Beginning at 08:10 PT, five follow-ups failed immediately.
• The problem persisted into 2026-07-18 after displayed plan usage reset to 0%.

Rejected follow-ups included:

• is it stopped or running? I do not see any activity tho
• hi
• WHAT IS HAPPENING?
• ANY UPDATE?
• what is happening brother?

Expected behavior

Codex should answer the benign follow-up or compact the task and continue.

Actual behavior

Each turn reaches the server, emits response.in_progress, and then ends with:

Request blocked.
codex_error_info: other

The task remains marked systemError. Restarting or retrying later does not recover it.

Relevant diagnostics

• Codex Desktop embedded CLI recorded as 0.145.0-alpha.18
• Transcript: approximately 51.5 MB
• Turns: 90
• Context compactions: 12
• Last recorded active input: approximately 188k tokens of a 258.4k context window
• Cumulative sampling tokens recorded across the task: approximately 276.7M
• Other tasks in the same account and project continue to work
• The final repository state completed cleanly before the blocking began

This looks like a long-thread compaction or backend thread-state guard permanently poisoning an otherwise benign task. Full logs and the original rollout were uploaded through /feedback under the thread ID above.