core: expose permission profile picker metadata#22928
Open
viyatb-oai wants to merge 1 commit into
Open
Conversation
Co-authored-by: Codex noreply@openai.com
This was referenced May 16, 2026
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
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.
Why
The
/permissionspicker needs a config-level way to distinguish legacy anonymous presets from named permission-profile mode. That signal cannot be inferred reliably in the TUI, especially for the edge case wheredefault_permissions = ":workspace"is present without a[permissions]table.What changed
default_permissions = ":workspace"case.Stack
/permissionsto the profile-aware TUI picker.Verification
cargo check -p codex-thread-manager-samplecargo test -p codex-core default_permissions_can_select_builtin_profile_without_permissions_tablecargo test -p codex-core permissions_profiles_allow_direct_write_roots_outside_workspace_root