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

Open 💬 6 comments Opened May 17, 2026 by kendonB

💡 Likely answer: A maintainer (etraut-openai, contributor) responded on this thread — see the highlighted reply below.

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_

View original on GitHub ↗

6 Comments

kendonB · 2 months ago

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.

etraut-openai contributor · 2 months ago

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

kendonB · 2 months ago

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

weathon · 1 month ago

yeah i am having the same issue

josh-padnick · 1 month ago

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.

kendonB · 1 month ago

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?