Feature: Persist approval policy selection to config.toml
Resolved 💬 2 comments Opened Dec 23, 2025 by Galaxy-0 Closed Mar 7, 2026
Problem
Currently, when a user changes the approval policy via the TUI (e.g., selecting 'Full Auto', 'Read-Only', or 'Untrusted' from the Approvals menu), the change is only effective for the current session. Restarting Codex causes it to revert to the default setting.
Proposed Solution
We should persist these changes to config.toml so that the user's preference is remembered across sessions.
Implementation Details
This would likely involve:
- Adding a
set_approval_policymethod toConfigEditsBuilder. - Dispatching a persistence event (e.g.,
PersistAskForApprovalPolicy) when the user selects a preset in the TUI. - Updating the
Appevent handler to write the new policy to disk.
(Note: Implementation logic was explored in closed PR #8474)
This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗