Thanks! I maintain stay-safe, an open-source linter for Codex config files. The network example helped me understand how Codex enforces domain rules.
If I enable network access, add a rule to block a domain, and leave the proxy off, does Codex warn me that commands can still reach that domain? In the 0.167.0 source, the only startup warning I found about a disabled proxy was about credential masking.
I’d like to get stay-safe’s warning right. I’ve linked the source lines for this question and four others below. If I’ve misread any of them, I’d appreciate a correction.
Deep dive on how the sandbox component of the Codex harness works.
Thanks! I maintain stay-safe, an open-source linter for Codex config files. The network example helped me understand how Codex enforces domain rules.
If I enable network access, add a rule to block a domain, and leave the proxy off, does Codex warn me that commands can still reach that domain? In the 0.167.0 source, the only startup warning I found about a disabled proxy was about credential masking.
I’d like to get stay-safe’s warning right. I’ve linked the source lines for this question and four others below. If I’ve misread any of them, I’d appreciate a correction.
https://github.com/chalkbadger/stay-safe/issues/124
This is the one it keeps escaping from?
No, that was Irregular's (they're Israeli and not in the US, hence why no prosecution under the CFAA).