Skip to content

Codex on Windows: live BAT execution rejected with no clear resolution steps #52830

Description

@balveer767

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

26.1002.52244

What subscription do you have?

Pro

What platform is your computer?

Windows 10 Pro, version 22H2, OS Build 19045.5371

What issue are you seeing?

Codex reported that execution of my local live-fetch BAT was rejected by its execution safety review, despite my explicit approval. The task recorded the status REJECTED_BY_APPLICABLE_TOOL_POLICY_REVIEW and stated that escalation was rejected. No live request was executed.
I cannot tell which specific condition caused the rejection or whether this is expected policy behavior or a configuration problem. There is no pending approval button visible in the task. I am requesting clarification and supported resolution steps, not a way to bypass safety controls.
The intended run covers five selected public GujRERA projects with fixed request limits. Offline tests pass, but live execution remains unverified. Public browser access works; I understand this does not establish automated-access permission.
In-app feedback ID: 01a10df7-dc76-7674-ba09-2e56f77f60fa

What steps can reproduce the bug?

Feedback ID: 01a10df7-dc76-7674-ba09-2e56f77f60fa

What is the expected behavior?

A clear explanation of the specific reason for denial and whether any supported, policy-compliant execution path exists. If an owner approval or configuration step is appropriate, please identify it. If this action is not permitted, please state that clearly. I am not requesting that safety controls be disabled or bypassed.

Additional information

Offline package tests pass, but live execution has not been verified. Ordinary public browser access succeeds; I understand that this does not establish permission for automated access. No proxy or security settings were changed to work around the denial.
In-app feedback has already been submitted under the ID above. Private project files, HAR contents, credentials and browser logs are intentionally not attached.

Observed sequence: I asked Codex to run a prepared local BAT for five selected projects, with 15 fixed sources per project, a maximum of 300 attempts including retries, no redirects and no dynamic document requests. I explicitly approved the run. The task reported rejection before any live request executed. No bypass or alternate execution was attempted. I have not established a minimal independently reproducible example.
Affected turn: 01a1245a-6f81-73c0-82ca-90627496c319
Observed on: 10 October 2026
The reported rejection status comes from the Codex task report, not a Windows error dialog.

Activity

  1. added
    appIssues related to the Codex desktop app
    on Oct 10, 2026
  2. added
    bugSomething isn't working
    windows-osIssues related to Codex on Windows systems
    sandboxIssues related to permissions or sandboxing
    on Oct 10, 2026
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 sandboxingwindows-osIssues related to Codex on Windows systems

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions