Keep Codex config writable for hook trust - #1
Draft
nickdichev wants to merge 2 commits into
Draft
Conversation
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
cdxwith the Home Manager-generated named profile~/.codex/config.tomlwritable so Codex can persist hook and project trustContext
Home Manager writes
~/.codex/home-manager.config.tomlas a symlink into the Nix store. When Codex is launched with--profile home-manager, hook approval attempts to persist trust throughconfig/batchWriteto that immutable profile and fail.This keeps MCP configuration declarative without making the active Codex configuration read-only.
Related upstream reports:
Verification
nix flake check --no-builddotfilesinputcdxalias ascodex --yologit diff --check