Full access mode still asks for approval after reconnecting to a remote environment

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

26.616.3767.0

What subscription do you have?

pro

What platform is your computer?

Microsoft Windows NT 10.0.26200.0 x64

What issue are you seeing?

When using the Codex desktop app with a remote environment in Full access mode, Codex sometimes still asks for approval before running commands.

This happens even though the session is configured with:

• Filesystem sandboxing: danger-full-access / Full access
• Approval policy: never / no approval expected

The issue appears most often after either:

• Restarting the Codex desktop app
• The remote connection being reset or reconnected

After reconnecting, the session appears to lose or desynchronize its permission state. The UI/configuration still indicates Full access, but command execution behaves as if approval is required.

Feedback ID: 019edea8-c39d-7c52-a0ca-6c80ece7b330

What steps can reproduce the bug?

Feedback ID: 019edea8-c39d-7c52-a0ca-6c80ece7b330

What is the expected behavior?

After the Codex desktop app restarts, or after a remote connection is reset and reconnected, the session should continue to honor the configured Full access mode.

Commands that are allowed under Full access should run without asking for additional approval.

Additional information

This seems like the app or remote session is not correctly restoring or synchronizing the sandbox/approval state after reconnection.

The issue is disruptive for long-running or automated development workflows because the user has to manually approve actions that should already be allowed by the selected Full access mode.