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

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.

Start by reviewing the uploaded conversation identified by thread ID 019ffd8a-67f6-7ea0-a21a-5454564d7acf and the reported cybersecurity safety block. Reproduce the interruption during a permitted read-only review with synthetic PostgreSQL data, then verify that the conversation either continues after the blocked segment or provides a clear recovery path without terminating the thread.