openai / openai/codex

Repeated “content can’t be shown” notices interrupt ordinary conversation

Open
#44,674 4 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

bug CLI safety-check
Dominant language
Rust
Stars
125k
Forks
19.4k
PR merge metrics
PR metrics pending

Description

What version of Codex CLI is running?

codex-cli 0.154.0

What subscription do you have?

PRO 200

Which model were you using?

gpt-6-Astra

What platform is your computer?

MacOS

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

No response

Codex doctor report

What issue are you seeing?

Using GPT-6 Astra in Codex CLI on macOS, I repeatedly receive:

“This content can’t be shown. Daybreak isn’t available for Astra. Some cybersecurity requests may still be limited.”

The notices also appear after simple requests to continue, acknowledge a message, or draft feedback about this problem. This prevents both completing the original task and reporting the interruption. Screenshots show the
sequence.

Please investigate whether these are false positives and why ordinary follow-up messages are affected.

Date: September 11, 2026, approximately 02:33–02:35, Asia/Jerusalem.

Diagnostics already uploaded. Thread ID: 01a08d77-b262-7f12-a5c2-23982f99867b.

What steps can reproduce the bug?

Uploaded thread: 01a08d77-b262-7f12-a5c2-23982f99867b

What is the expected behavior?

you really asking? calm down your guardrails!!!!!!!

Additional information

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the uploaded thread 01a08d77-b262-7f12-a5c2-23982f99867b and the already-uploaded diagnostics; the issue names no files, tests, or entry points. Done means determining whether the notices are false positives and why ordinary follow-up messages are affected.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
cli, security
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.