Issue Station
Sign In
Tools hereToolbox

codex - 💡(How to fix) Fix `/permissions` changes do not propagate to the active session in `codex-cli 0.124.0` [7 comments, 7 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openai/codex#19256•Fetched 2026-04-24 10:40:00
View on GitHub
Comments
7
Participants
7
Timeline
17
Reactions
1
Author
wypongwypong
Participants
christiandoxachristiandoxadecentralizedblack-makerdecentralizedblack-makeretraut-openaietraut-openaigithub-actions[bot]github-actions[bot]mahmoud1973mahmoud1973sjtianwensjtianwenwypongwypong
Timeline (top)
commented ×7labeled ×5cross-referenced ×2closed ×1
RAW_BUFFERClick to expand / collapse

What version of Codex CLI is running?

codex-cli 0.124.0

What subscription do you have?

GPT-EDU

Which model were you using?

gpt-5.4

What platform is your computer?

Linux

What terminal emulator and version are you using (if applicable)?

st

What issue are you seeing?

Changes made through /permissions are saved in the UI/config flow, but they do not take effect in the current session. The active session continues using the old permission state.

In practice, changing permissions such as approval mode or sandbox behavior via /permissions appears to update the setting surface, but the running thread still behaves as if the previous session permissions are still active.

What steps can reproduce the bug?

  1. Start a Codex session.
  2. Run /status and note the current permission state.
  3. Run /permissions.
  4. Change the permission setting to a different mode, for example switching to Full Access.
  5. Return to the same session.
  6. Ask codex to report sandox, approval status shows that nothing has changed.

What is the expected behavior?

After granting 'Full Access' from \permissions, it should be Filesystem sandbox: danger-full-access Approval policy: never Network access: enabled

Additional information

No response

extent analysis

TL;DR

The issue can be mitigated by restarting the Codex session after updating permissions through /permissions.

Guidance

  • Verify that the permissions are correctly updated in the UI/config flow after running /permissions.
  • Try restarting the Codex session after updating permissions to see if the changes take effect.
  • Check if there are any other settings or configurations that might be overriding the permission changes.
  • Test the permission changes with a new session to confirm if the issue is specific to the current session.

Example

No code snippet is provided as it is not necessary for this issue.

Notes

The issue seems to be related to the session not refreshing after permission changes. Restarting the session might be a temporary workaround until a permanent fix is available.

Recommendation

Apply workaround: Restart the Codex session after updating permissions, as it seems to be the most straightforward way to ensure the changes take effect.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#callback error#memory management#API rate limit#retriever error#indexing error

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

codex - 💡(How to fix) Fix `/permissions` changes do not propagate to the active session in `codex-cli 0.124.0` [7 comments, 7 participants]