Codex app automations have a "never" approval policy and can't escalate
Open 💬 2 comments Opened May 30, 2026 by anorth2
💡 Likely answer: A maintainer (github-actions[bot], contributor)
responded on this thread — see the highlighted reply below.
What version of the Codex App are you using (From “About Codex” dialog)?
26.527.31326
What subscription do you have?
Pro ($100)
What platform is your computer?
macOS (Apple Silicon)
What issue are you seeing?
In interactive mode sessions are able to escalate approvals for actions like docker socket interactions and running curl commands.
When triggered as an automation they have a "never" escalation policy. This hinders their capabilities since they can't interact with various tools (i.e. sending a curl to ntfy to trigger a phone notification)
What steps can reproduce the bug?
Create an automation that uses curl and notice it can't run curl.
What is the expected behavior?
It should trigger escalation and approval policies and trigger the curl command.
Additional information
_No response_
2 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
Same
I’m seeing the same behavior on Codex Desktop for Windows.
Evidence:
config.tomlhas:``
toml
``[sandbox_workspace_write]
network_access = true
``
toml
``execution_environment = "local"
sandbox_policy.type = workspace-writenetwork_access = falsedanger-full-access, and the exact same network-dependent steps then work.Seems like the cron/scheduled automation wakeup path is not respecting the local sandbox/network configuration, even though normal interactive continuation can.