Unexpected Safety Check
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.5k
- PR merge metrics
- PR metrics pending
Description
What version of Codex CLI is running?
codex-cli 0.146.0
What subscription do you have?
pro
Which model were you using?
gpt-5.6-sol
What platform is your computer?
Linux 6.8.0-136-generic x86_64 x86_64
What terminal emulator and version are you using (if applicable)?
No response
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
What steps can reproduce the bug?
Uploaded thread: 019fcbec-2420-7de1-917b-9a0080f26417
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 referenced in the reproduction steps (019fcbec-2420-7de1-917b-9a0080f26417) and confirm what request triggered the safety warning. The issue does not include the request content or expected behavior, so clarify those before locating the relevant code or tests. Done means the behavior is reproducible and the warning matches the agreed expected behavior.
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
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100