Codex app: composer remains disabled after “This request was blocked by our safety systems”

What version of the Codex App are you using (From “About Codex” dialog)?

26.826.12353

What subscription do you have?

ChatGPT Plus (personal workspace)

What platform is your computer?

"$([Environment]::OSVersion.VersionString) $(if ([Environment]::Is64BitOperatingSystem) {'x64'} else {'x86'})"

What issue are you seeing?

In one local Codex thread, a turn ended with the message:

“This request was blocked by our safety systems.”

Immediately afterward, the message composer in that thread became disabled. I can no longer type or send any follow-up message in the affected thread.

Other threads in the same Codex app and the same local project still accept input normally. The affected thread remains visible, and its local file changes are still present.

The task was a personal quantitative-research software project involving a bounded financial-data collection workflow. It was not a cybersecurity, malware, exploit, credential-access, or unauthorized-access task.

The affected thread title is:
“识别项目规则和四个自定义子 Agent”

The app did not display a detailed reason, error code, review option, or method to restore the composer. I cannot determine whether this is an intended permanent thread restriction or a client UI bug following a safety block.

What steps can reproduce the bug?

Feedback ID: 01a05867-80cd-7ec0-b275-f34b2cd293e4

What is the expected behavior?

A blocked turn should stop the affected request, but the thread composer should remain available for safe follow-up questions, clarification, or requesting a review.

If the entire thread must remain restricted, the app should clearly explain that the restriction is thread-level, provide a non-destructive review or appeal path, and preserve the existing conversation and local file changes.

Additional information

Feedback ID: 01a05867-80cd-7ec0-b275-f34b2cd293e4

The problem is isolated to one thread. Other threads in the same app and local project remain usable.

A separate old thread has a “Model provider 'custom' not found” configuration error. That is a different thread and should not be treated as the cause of this composer-disablement issue.

I can provide additional non-sensitive diagnostics if requested. I have not included API keys, tokens, authorization files, full session transcripts, or private project data.

Start at the Codex app's composer state handling for a turn that ends with “This request was blocked by our safety systems,” and compare it with a normal thread. Use the provided Feedback ID and the isolated-thread behavior to investigate whether the disabled composer is intentional or a client bug; done means safe follow-up input remains available or the restriction is clearly explained with a recovery path.