Skip to content

[macOS] Sites publishing blocked by granular sandbox_approval=false despite Full access enabled #50069

Open

Description

@ameerelnasri1969-lab

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

Exact version unavailable; observed October 1, 2026 in the desktop app.

What subscription do you have?

Not verified

What platform is your computer?

Darwin 27.0.0 arm64 arm

What issue are you seeing?

Publishing a prepared static website through Sites fails before stdin reaches the official publishing workflow. The app General settings show Full access enabled, but the active session still reports workspace-write, restricted network, and a granular approval policy with sandbox_approval=false.

Exact error:

write_stdin rejected: approval required by policy, but AskForApproval::Granular.sandbox_approval is false

The cause of the discrepancy between settings and effective session policy is unknown.

What steps can reproduce the bug?

  1. In the desktop app on macOS, enable Full access in General settings.
  2. Ask the agent to publish a prepared static website with the Sites plugin.
  3. The agent requests network and repository write permissions through request_permissions. The request returns granted for the turn with strict_auto_review=true.
  4. Launch the bundled site-workflow.mjs with tty:true. It prints: Ready for Site workflow JSON on stdin (input is hidden).
  5. Send the workflow JSON through write_stdin. The call is rejected with the error above, before execution.

Restarting the app and retrying in a new local conversation did not resolve the issue.

What is the expected behavior?

The effective permissions should match the selected supported permission mode, or the app should clearly explain any higher-priority restriction and provide the supported approval path. Authorized publishing should not end in an unexplained mismatch.

Additional information

Observed October 1, 2026 (Asia/Riyadh). Site registration and read-only Sites calls work; source publication has not completed. No credentials, private source, account email, or property details are included in this report. The Help Center AI suggested filing an engineering issue.

Activity

  1. added
    bugSomething isn't working
    sandboxIssues related to permissions or sandboxing
    tool-callsIssues related to tool calling
    on Oct 1, 2026
  2. ashni02 commented on Oct 4, 2026

    @ashni02

    I’m seeing the same error on macOS while publishing an existing Sites website, with Ask for approval selected: write_stdin rejected: approval required by policy, but AskForApproval::Granular.sandbox_approval is false. I also submitted in-app feedback: 01a103d7-3102-7c03-b84d-d0dbc8bca63c. My pending changes remain unpublished.

  3. eleecn90 commented on Oct 13, 2026

    @eleecn90

    Additional reproduction on macOS while updating an existing private ChatGPT Site.

    The local change and build checks completed. The official site-workflow.mjs helper started in a TTY and waited for its documented hidden JSON input. The subsequent write_stdin call was rejected before the workflow received the credential:

    write_stdin rejected: approval required by policy, but AskForApproval::Granular.sandbox_approval is false
    

    Sending Ctrl-C through the same tool was also rejected, so helper termination could not be confirmed through that session. Reconnecting the desktop did not establish a working approval path. The intended Site update was not published.

    I had explicitly authorized publishing the Site update. The exact affected app/plugin build and the source of the effective approval policy have not been independently established, so this report does not claim that the UI setting or a particular release caused the problem.

    Could maintainers clarify the supported, least-privilege path for the official Sites stdin handoff and cancellation under this policy? A preflight rejection before starting an unusable interactive helper would also help. I am not requesting disabled protections or an alternate token transport.

    No credentials, raw logs, private URLs, local paths or session identifiers are attached.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    appIssues related to the Codex desktop appbugSomething isn't workingsandboxIssues related to permissions or sandboxingtool-callsIssues related to tool calling

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions