Conversation
bolinfest
force-pushed
the
pr4220
branch
4 times, most recently
from
9415870 to
943b8af
Compare
pakrym-oai
approved these changes
Sep 25, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Because the
codexprocess could contain sensitive information in memory, such as API keys, we add logic so that whenCODEX_SECURE_MODE=1is specified, we avail ourselves of whatever the operating system provides to restrict observability/tampering, which includes:ptrace(2), so it is not possible to attach to the process with a debugger, such asgdbAdmittedly, a user with root privileges can defeat these safeguards.
For now, we only add support for this in the
codexmultitool, but we may ultimately want to support this in some of the smaller CLIs that are buildable out of our Cargo workspace.