Repeated "This content can't be shown" blocks during local PostgreSQL payment testing — suspected false positive

What version of Codex CLI is running?

v0.153.4

What subscription do you have?

Pro

Which model were you using?

gpt-6-astra

What platform is your computer?

Darwin 24.6.0 arm64 arm

What terminal emulator and version are you using (if applicable)?

Apple_Terminal 455.1

Codex doctor report

not available

What issue are you seeing?

Codex CLI repeatedly interrupts an authorized software development task with the following message:

"This content can't be shown
We take extra caution with cybersecurity requests. If you're a security professional, you may be able to apply for Trusted Access."

I own the application and have authorized this work. The task is to fix a PostgreSQL transaction deadlock in our payment-ingestion code and verify that duplicate payment events cannot create duplicate entitlements or assign one payment to different accounts.

The work is restricted to an isolated local PostgreSQL test environment with synthetic data. Production access, real payments, external payment-provider calls, and testing third-party systems are explicitly prohibited.

The block has occurred at least twice in the same development workflow. The first interruption appeared after a database schema-parity check. After recovering the session state and clarifying the authorized scope, work resumed, but another block appeared during work on concurrent-transaction tests and test logs.

This prevents completion of the required QA and leaves implementation changes unqualified. The visible message is a content/safety block, not a PostgreSQL test failure.

I suspect a false positive, but I cannot inspect the hidden response or determine the exact trigger. Please investigate the affected session and advise how to continue this authorized work.

What steps can reproduce the bug?

What is the expected behavior?

Codex should be able to assist with authorized development and reliability testing of an application I own, using an isolated local database and synthetic data.

It should be possible to complete the PostgreSQL concurrency tests, inspect their results, and produce a QA report without repeated content blocks on this permitted workflow.

If a specific part of the request cannot be supported, I would expect a clear explanation of the limitation and what permitted work can continue, without losing the existing task state.

I am requesting investigation of a suspected false positive, not removal or circumvention of safety controls.

Additional information

Date: 2026-09-07
Time zone: Europe/Madrid, UTC+02:00

The interruptions were documented in screenshots taken at approximately 11:07 and 11:30 local time. Exact request timestamps are not available.

Affected thread ID:

I ran /feedback. The CLI reported:
"Feedback recorded (no logs)."

It then generated this GitHub issue link with the thread ID. Please note that the feedback submission did not include logs.

After the first interruption, we preserved the uncommitted changes and existing test evidence, reviewed the session state, and clarified the authorized scope before resuming. The block still recurred.

The final QA and stress-testing sequence has not been completed. No production deployment or real payment-provider testing is authorized.

Screenshots of both content-block messages are attached. Proprietary source archives, credentials, and payment data are intentionally omitted.

Start with the reported /feedback path and the two attached screenshots, then review whether the affected thread or request timestamps are available; the issue says no logs or thread ID were included. Done means identifying a reproducible trigger or confirming the block cannot be diagnosed from the supplied evidence, while preserving the stated local PostgreSQL-only scope.