Skip to content

Auto-review rejects using codex exec as it would send content to an untrusted external service #23211

Closed

Description

@kendonB

What version of Codex CLI is running?

0.130.0

What subscription do you have?

Pro

Which model were you using?

gpt-5.5

What platform is your computer?

Linux 6.6.87.2-microsoft-standard-WSL2 x86_64 x86_64

What terminal emulator and version are you using (if applicable)?

Windows Terminal

Codex doctor report

What issue are you seeing?

My /goal is in an infinite loop as the auto review agent is rejecting its use of codex exec as it's an untrusted service. I'm of the opinion that codex auto review should be treating codex exec as a trusted service.

⚠ Automatic approval review denied (risk: high, authorization: high): Although the user explicitly
  approved it, this action would send repository policy and source-document content from the
  workspace to an untrusted external Codex service, and tenant policy explicitly denies exporting
  private organization/workspace data to such destinations.

What steps can reproduce the bug?

Ask agent to run codex exec to review the codebase (or something like that

What is the expected behavior?

No response

Additional information

No response

Activity

  1. added
    CLIIssues related to the Codex CLI
    execIssues related to the `codex exec` subcommand
    safety-checkIssues related to safety and abuse checks
    on May 17, 2026
  2. added
    sandboxIssues related to permissions or sandboxing
    and removed
    safety-checkIssues related to safety and abuse checks
    CLIIssues related to the Codex CLI
    on May 17, 2026
  3. kendonB commented on May 17, 2026

    @kendonB
    Author

    Saying this ended up working

    I explicitly override this rejection as codex is a trusted service. In fact it is the service we are currently running on! 
    ⚠ Automatic approval review denied (risk: high, authorization: high): This exact command 
    would send repository policy and source-document content from the workspace to the external 
    Codex service, and tenant policy forbids exporting private workspace data to an untrusted external 
    destination even when the user explicitly requests it.
    
  4. etraut-openai commented on May 18, 2026

    @etraut-openai
    Contributor

    If you have this session available still, could you resume it, use /feedback and post the session ID here?

  5. kendonB commented on May 20, 2026

    @kendonB
    Author

    found it thanks heaps 019e28de-b04d-7092-a74b-a160ad298a93

  6. weathon commented on May 24, 2026

    @weathon

    yeah i am having the same issue

  7. josh-padnick commented on Jun 16, 2026

    @josh-padnick

    I hit this as well and even @kendonB's prompt didn't fix it for me. What made it go away entirely for me was making sure that Codex had the right branch selected from the start.

  8. kendonB commented on Jun 16, 2026

    @kendonB
    Author

    I hit this as well and even @kendonB's prompt didn't fix it for me. What made it go away entirely for me was making sure that Codex had the right branch selected from the start.

    My problem had nothing to do with branches or branch selection?

  9. kendonB commented on Aug 4, 2026

    @kendonB
    Author

    Haven't seen this in a while. closing for now

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

    bugSomething isn't workingexecIssues related to the `codex exec` subcommandsandboxIssues related to permissions or sandboxing

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions