False cybersecurity warning repeatedly hides normal infrastructure workflow output

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

Codex version

codex-cli 0.146.0

Problem

During a normal, authorized infrastructure/software engineering session, the UI repeatedly inserts:

This content can't be shown We take extra caution with cybersecurity requests...

The work is not cybersecurity-related. It consists of ordinary repository edits, unit tests, build artifact validation, and cloud infrastructure operations for an internal company project.

Impact

  • The banner appears repeatedly between normal assistant/tool updates.
  • It makes the operator believe execution stopped or content was blocked.
  • Tool commands can still run, so the warning appears to be a false-positive presentation/classification issue rather than an actual command denial.
  • Repeated banners significantly disrupt progress visibility in a long-running operational session.

Reproduction

  1. Open a Codex CLI session in a regular infrastructure repository.
  2. Perform normal Python/C++ build preparation and unit-test work.
  3. Discuss a lifecycle/concurrency test for a database client library.
  4. Observe repeated cybersecurity warning banners after otherwise normal assistant turns.

Expected behavior

Normal infrastructure engineering content should render normally. If content is actually blocked, the UI should identify the specific blocked operation and distinguish it from hidden internal reasoning or a harmless presentation warning.

Privacy

Project-specific names, hostnames, credentials, logs, and screenshots are intentionally omitted because the affected session concerns private production infrastructure.

View original on GitHub ↗

2 Comments

github-actions[bot] contributor · 26 days ago

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

  • #36102
  • #35862
  • #35651

Powered by Codex Action

jselvareef · 26 days ago

Recurrence confirmed again on 2026-08-02 while editing ordinary Markdown operational documentation for an enterprise database lifecycle fix. The banner was triggered immediately after a normal apply_patch that only updated CHANGELOG/runbooks with test results and rollback notes; the command itself succeeded. This continues to interrupt/obscure the primary thread despite no cybersecurity request. New local screenshot evidence: /tmp/codex-clipboard-ZQ5ITb.png (available on the reporter workstation). Terms visible near the recurrence include lifecycle, callback timeout, hashes, process exit, canary, rollback, PROD, and service; none is a security task.