From 36aa6b924528a94f533f6b52587cf2ef0e2f150e Mon Sep 17 00:00:00 2001
From: BigSimmo <87357024+BigSimmo@users.noreply.github.com>
Date: Thu, 30 Jul 2026 20:46:41 +0800
Subject: [PATCH 1/2] docs(codex): route authorised GitHub tasks through
 connector

---
 AGENTS.md | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/AGENTS.md b/AGENTS.md
index e44efbdff..2910e95e9 100644
--- a/AGENTS.md
+++ b/AGENTS.md
@@ -843,6 +843,14 @@ Use `docs/codex-cloud.md` as the environment contract:
 - The Codex GitHub connection used to clone a repository is separate from agent-shell
   `git push` or `gh` authentication. Reconnect the repository in Codex settings if a
   controlled write test cannot publish; never add a PAT to Cloud variables or secrets.
+- For an explicitly authorised GitHub task, use the authenticated GitHub connector/MCP
+  tools as the default remote control plane. Use them for repository, PR, issue, review
+  thread, and Actions work, including inline-thread replies/resolution and approved branch,
+  file, or PR mutations. Missing `gh`, shell GitHub credentials, or direct shell network
+  access is not a loss of this capability and must not prompt a PAT workaround.
+- Confirm the exact repository and PR/thread/job before a write. If the connector lacks a
+  needed GitHub setting or organisation control, report that limit rather than attempting a
+  credential, secret, or shell-based bypass.
 - Cloud browser proof is Playwright/Chromium, Firefox, or WebKit container evidence, not
   physical iPhone Safari/PWA acceptance.
 

From 623024314d4f66c893c830f873f69155d494f904 Mon Sep 17 00:00:00 2001
From: BigSimmo <87357024+BigSimmo@users.noreply.github.com>
Date: Thu, 30 Jul 2026 20:46:50 +0800
Subject: [PATCH 2/2] docs(codex): document GitHub connector routing

---
 docs/codex-cloud.md | 10 +++++++++-
 1 file changed, 9 insertions(+), 1 deletion(-)

diff --git a/docs/codex-cloud.md b/docs/codex-cloud.md
index 2feaf9a69..63e55aff5 100644
--- a/docs/codex-cloud.md
+++ b/docs/codex-cloud.md
@@ -78,10 +78,18 @@ Selecting `BigSimmo/Database` proves that the Codex GitHub connection can discov
 clone the repository. Codex can also show task diffs and offer pull-request workflows
 through its GitHub integration when that installation has write permission.
 
+For an explicitly authorised GitHub task, treat the authenticated GitHub connector/MCP
+tools as the default remote control plane. Use the connector for repository and PR reads,
+issue and PR comments, inline-review-thread replies/resolution, Actions logs/retries, and
+approved branch, file, or PR mutations. Do not infer that GitHub is unavailable because
+`gh`, shell GitHub credentials, or direct shell access are absent.
+
 GitHub connector permission is separate from credentials inside the agent shell. Do
 not add a personal access token to Cloud secrets or environment variables to make
 `git push` or `gh` work. If a Cloud task cannot publish a branch, reconnect the
-repository in Codex settings and run a controlled branch/PR write test.
+repository in Codex settings and run a controlled branch/PR write test. If the connector
+does not expose a required repository/organisation setting, report the limit rather than
+attempting a credential or secret workaround.
 
 ## First Cloud task