codex - 💡(How to fix) Fix /review invokes GitHub MCP tools despite explicit local-only restriction [1 comments, 1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openai/codex#21222Fetched 2026-05-06 06:24:38
View on GitHub
Comments
1
Participants
1
Timeline
6
Reactions
0
Participants
Timeline (top)
labeled ×5commented ×1

Root Cause

I repeatedly stated that GitHub MCP tools were not allowed. Despite that, the review flow attempted to use GitHub MCP tooling. This creates a trust and privacy issue because repository review may unexpectedly access connected GitHub integrations when the user requests local-only operation.

RAW_BUFFERClick to expand / collapse

What version of Codex CLI is running?

0.128.0

What subscription do you have?

ChatGPT Pro (5x)

Which model were you using?

gpt-5.5

What platform is your computer?

Linux 6.17.0-19-generic x86_64 x86_64

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

No response

What issue are you seeing?

The /review workflow now calls GitHub MCP connector tools, such as codex_apps.github_list_repositories, even when I explicitly say that GitHub MCP tools are not allowed and the review must use only the local shell and git CLI.

This is a behavior change. /review previously did not invoke GitHub MCP tools for local repository review.

What steps can reproduce the bug?

Uploaded thread: 019df92d-4b2d-74b3-87cb-db4b5332dd96

What is the expected behavior?

When a user prohibits GitHub MCP tools, /review should honor that constraint and perform the review using only local filesystem access, shell commands, and git CLI.

Additional information

I repeatedly stated that GitHub MCP tools were not allowed. Despite that, the review flow attempted to use GitHub MCP tooling. This creates a trust and privacy issue because repository review may unexpectedly access connected GitHub integrations when the user requests local-only operation.

extent analysis

TL;DR

The issue can be mitigated by reconfiguring the /review workflow to explicitly exclude GitHub MCP tools when local-only operation is requested.

Guidance

  • Review the configuration of the /review workflow to ensure it honors the constraint of not using GitHub MCP tools when explicitly prohibited.
  • Check the uploaded thread 019df92d-4b2d-74b3-87cb-db4b5332dd96 for any clues on how the workflow is currently configured and where it might be invoking GitHub MCP tools.
  • Verify that the codex_apps.github_list_repositories tool is not being called unnecessarily by the /review workflow when local-only operation is requested.
  • Consider adding additional logging or debugging statements to the /review workflow to understand why it is invoking GitHub MCP tools despite the prohibition.

Notes

The issue seems to be related to a behavior change in the /review workflow, and the exact cause is not immediately clear. Further investigation into the workflow configuration and the uploaded thread is necessary to determine the root cause.

Recommendation

Apply workaround: Reconfigure the /review workflow to explicitly exclude GitHub MCP tools when local-only operation is requested, as this is the most direct way to address the trust and privacy issue described.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

codex - 💡(How to fix) Fix /review invokes GitHub MCP tools despite explicit local-only restriction [1 comments, 1 participants]