Skip to content

docs(codex): route authorised GitHub tasks through connector#1449

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
BigSimmo merged 2 commits into from
Jul 30, 2026
Merged

docs(codex): route authorised GitHub tasks through connector #1449

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
36aa6b9
docs(codex): route authorised GitHub tasks through connector
BigSimmo Jul 30, 2026
6230243
docs(codex): document GitHub connector routing
BigSimmo Jul 30, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions AGENTS.md
View file
Open in desktop
Original file line numberDiff line numberDiff line change
Expand Up@@ -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.

Expand Down
10 changes: 9 additions & 1 deletion docs/codex-cloud.md
View file
Open in desktop
Original file line numberDiff line numberDiff line change
Expand Up@@ -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

Expand Down
Loading