›_ Codex Issues
Codex Issues / #38464

Conversation interrupted during read-only security review after content-safety block

Open 💬 2 comments Opened Aug 14, 2026 by Dokuvena
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

Summary

A Codex conversation was interrupted during a read-only local security review after the UI displayed a cybersecurity safety block (This content can't be shown). The interruption occurred while Codex was continuing a previously approved review workflow and had been instructed not to modify project files.

Thread ID

019ffd8a-67f6-7ea0-a21a-5454564d7acf

Observed behavior

  • The review was running local, non-persistent PostgreSQL concurrency probes against synthetic test data.
  • The UI then showed the cybersecurity caution message and the conversation was interrupted.
  • /feedback was used and reported: Feedback recorded (no logs).
  • Codex suggested opening this issue and referencing the thread ID.

Expected behavior

The conversation should remain usable after a blocked tool/output segment so that the model can continue the permitted read-only review, or provide a clear recoverable path without terminating the thread.

Privacy / security

No local filesystem paths, credentials, secrets, or customer data are included in this issue. The thread ID above can be used by OpenAI staff to locate the uploaded thread if available.

View original on GitHub ↗

2 Comments

github-actions[bot] contributor · 14 days ago

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

  • #37702
  • #37854

Powered by Codex Action

shleder · 13 days ago

The interruption here is useful to separate two possibilities: an upstream safety/policy interruption with an otherwise intact rollout, versus a persisted unfinished boundary left behind when the conversation stopped.

If the affected local rollout still exists, could you run a read-only Codex Rescue 0.1.0a3 doctor check?

pipx install codex-rescue==0.1.0a3
codex-rescue sessions
codex-rescue doctor --latest

No salvage needed. If the affected thread is not the latest one, please don't mutate or rename anything to make it latest; just say so.

A HEALTHY result is still useful: in Rescue, that only means no recognized structural/persistence issue was found in the analyzed rollout. It does not mean the safety interruption itself was valid or repaired. If it reports an unfinished/corrupted boundary instead, that gives a different recovery signal.

Please share sanitized status/findings only — no raw rollout, prompts, security-review content, repository data, local paths, IDs, database files, credentials, or secrets.

https://github.com/shleder/codex-rescue