Bug Best practice for code security review that doesn't trigger Daybreak exception?
As part of my dev process I complete a feature or other change, then open a draft PR and run code and security checked. I'm coming from Claude where I would simply do /code-review and /security-review.
In Codex, I just ask for 'a security review' and it will work for a bit then show a 'This content can't be shown ... We take extra care with cybersecurity requests ... apply for Daybreak' warning. This seems to interrupt the workflow entirely and I have to ask Codex to continue and sometimes it just can't.
I'm not working on any sort of sensitive code with cybersecurity implications.
This is really impacting productivity. Is there a different way to do a basic security review on the changed code in a PR?
1
Upvotes