"This content can't be shown We take extra caution with cybersecurity requests." when codex is testing their own brand new code according to their own work plan.
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
What version of Codex CLI is running?
0.148
What subscription do you have?
Codex pro
Which model were you using?
5.6 sol
What platform is your computer?
No response
What terminal emulator and version are you using (if applicable)?
Linux 6.12.90+deb13.1-amd64 x86_64
Codex doctor report
What issue are you seeing?
ⓘ 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.
Trusted Access: https://openai.com/form/enterprise-trusted-access-for-cyber/
Learn more: https://help.openai.com/en/articles/20001326
Message received repeatedly when working on project containing code which is 100% written in house & has nothing to do with cyber security. I know others have had this kind of "you are allowed to write code but you are not allowed to test it" problem. I am posting this here because this is what the instructions in the TUI app told me to do.
What steps can reproduce the bug?
Uploaded thread: 019ff27a-8eea-7c30-a585-c1cd5a62465d
What is the expected behavior?
No response
Additional information
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the uploaded thread 019ff27a-8eea-7c30-a585-c1cd5a62465d and reproducing the repeated warning with Codex CLI 0.148 on Linux. Compare the project content and requested work with the conditions that trigger the cybersecurity message; done means identifying and correcting the false positive without weakening the intended safety behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux, rust
- Domain
- cli, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100