|
|
|
|
|
|
by dangelosaurus
10 hours ago
|
|
|
Fair question, and I agree the refusals are frustrating. The CLI doesn't do a repository-ownership check. Public projects are supported, and reviewing your own Linux kernel patches is the kind of defensive work we want to support. The refusals come from model guardrails, which can be overly cautious. Trusted Access for Cyber (TAC1/Daybreak) is a separate, approved access path that can reduce those refusals. If you're an open-source maintainer, you can apply for conditional Codex Security access here:
https://openai.com/form/codex-for-oss/ For enterprise teams, the Daybreak onboarding process is explained here:
https://help.openai.com/en/articles/20001261-enterprise-dayb... If you have a specific repro, I'd be happy to look into it. |
|
|