Skip to content

core: expose permission profile picker metadata#22928

Open
viyatb-oai wants to merge 1 commit into
mainfrom
codex/viyatb/profile-permissions-config
Open

core: expose permission profile picker metadata#22928
viyatb-oai wants to merge 1 commit into
mainfrom
codex/viyatb/profile-permissions-config

Conversation

@viyatb-oai
Copy link
Copy Markdown
Collaborator

@viyatb-oai viyatb-oai commented May 15, 2026

Why

The /permissions picker 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 where default_permissions = ":workspace" is present without a [permissions] table.

What changed

  • Expose whether the merged config is explicitly in permission-profile mode.
  • Expose the configured custom permission profile IDs alongside the built-in profile semantics.
  • Add regression coverage for profile mode detection and custom profile metadata, including the default_permissions = ":workspace" case.
  • Update the thread-manager sample config literal to match the expanded config shape.

Stack

  1. This PR: config metadata needed by downstream permission-profile consumers.
  2. #22931: refresh active permission profiles through runtime/session/network state.
  3. #21559: switch /permissions to the profile-aware TUI picker.

Verification

  • cargo check -p codex-thread-manager-sample
  • cargo test -p codex-core default_permissions_can_select_builtin_profile_without_permissions_table
  • cargo test -p codex-core permissions_profiles_allow_direct_write_roots_outside_workspace_root

Co-authored-by: Codex noreply@openai.com
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant