Full access mode doesn't work after the app restart

Open
#36,816 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
rust

Research direction

Reproduce the restart sequence on the reported Codex App version and Darwin arm64 platform: enable “Full access,” start a goal needing elevated privileges, restart the app, and observe the next elevated action. Trace where the permission profile is restored or re-declared after restart. Done means the selected mode remains effective and no unexpected approval prompt appears.

Written by the indexing model from the issue text.

Description

app bug sandbox
What version of the Codex App are you using (From “About Codex” dialog)?

26.727.51351

What subscription do you have?

Pro x20

What platform is your computer?

Darwin 25.5.0 arm64 arm

What issue are you seeing?

I keep asked for approvals despite using "Full access" mode

What steps can reproduce the bug?

Use "Full access" mode
Start a goal that requires some elevated privileges
Close the app
Start the app

The goal will continue automatically but then when some elevated action it will ask for permission, ignoring the "Full access" mode.

What is the expected behavior?

No response

Additional information

That is what codex has to say about this:

Why do I get those "approve" prompts despite "full access" mode active?

< Because this task’s permission profile changed mid-run. It started as unrestricted with approval policy never, but the latest environment context re-declared it as managed workspace-write with network access restricted. “Full access” still covers the repository filesystem, but production network calls are separately gated.

Dominant language
Rust
Stars
125k
Forks
19.5k
Avg merge
1m
Merged PRs (30d)
1k

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from openai/codex

All issues in openai/codex

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.