What issue are you seeing?
Product/Area:
ChatGPT Work / Codex / GitHub connector
Severity:
High
Summary:
Codex using the 5.6 model path repeatedly failed to complete a real GitHub PR branch update, claiming the environment did not have the capability to access or update the actual PR branch. The same task was then run with the 5.5 model path and succeeded using the GitHub connector.
This suggests the GitHub connector, repository permissions, and user-side authentication are valid, and the failure is specific to 5.6’s tool discovery, connector routing, branch-write reasoning, or capability detection.
Repository:
thochaos/madison-pm-deploy
Affected PR:
PR 116
Task requested:
Resolve conflicts on the actual GitHub branch for PR 116 against current main. Do not merge or deploy.
Conflicted files reported by GitHub:
- build.json
- checklist.js
- index.html
- sw.js
- test-checklist-pass-rate.js
Actual behaviour under 5.6:
Multiple 5.6 runs failed or stopped, reporting that the environment could not update the actual GitHub branch or lacked real GitHub branch-write capability. The failures implied the task could only be done locally or not at all.
This was incorrect.
Actual behaviour under 5.5:
The same class of task was run under 5.5 and succeeded.
5.5 was able to:
- Detect GitHub connector push/admin access
- Read PR 116 metadata
- Identify the real head branch: codex/fix-post-inspection-summary-pass-rate-bug
- Incorporate current main SHA: b1679359d6be488462335dd6da70b7e450e0fdaf
- Resolve the reported conflicts
- Push an actual GitHub-visible update to the PR branch
- Reopen/verify the PR after a connector-side branch update issue
- Confirm the PR was open, not merged, mergeable, and behind_by 0
Successful final result from 5.5:
PR: https://github.com/thochaos/madison-pm-deploy/pull/116
Final PR branch head:
de9e97f83856e07b147154da4e52135ec604e840
Current main incorporated:
b1679359d6be488462335dd6da70b7e450e0fdaf
GitHub state after 5.5 run:
- Open
- Not merged
- Mergeable
- behind_by: 0
- ahead_by: 8
Why this matters:
This appears to rule out:
- Broken GitHub connector installation
- Missing repository permission
- User-side GitHub token/authentication issue
- Lack of branch-write access in general
The same connector and repository access worked under 5.5. The blocker appears specific to the 5.6 Work/Codex model path.
Suspected issue:
5.6 may be failing in one or more of these areas:
- GitHub connector tool discovery
- Connector capability detection
- Choosing connector-backed GitHub APIs over local-only git assumptions
- Reasoning about actual PR branch write capability
- Correctly distinguishing local checkout limitations from connector capabilities
Requested investigation:
Please investigate why Codex 5.6 failed to use available GitHub connector capabilities that Codex 5.5 successfully used for the same repository, PR, and branch-update workflow.
What steps can reproduce the bug?
-
Open ChatGPT Work/Codex using the 5.6 model path.
-
Use a workspace with the GitHub connector installed and connected to a repository where the connector has branch write access.
-
Ask Codex to update an actual GitHub PR branch, not a local-only branch. In my case:
Repository: thochaos/madison-pm-deploy
PR: 116
Task: resolve conflicts against current main, commit the result to the real PR branch, and do not merge or deploy.
-
Include instructions that local git clone/fetch/auth failure should not be treated as a blocker if the GitHub connector can read and write the actual branch.
-
Observe that Codex 5.6 fails or stops, claiming it cannot access/update the real PR branch or that only local changes are possible.
-
Repeat the same task using the 5.5 model path.
-
Observe that 5.5 successfully uses the GitHub connector, detects branch write access, reads the PR metadata, updates the actual PR branch, and reports the GitHub-visible final branch head SHA.
What is the expected behavior?
Expected behaviour:
Codex should use the available GitHub connector to:
- Read PR metadata
- Identify PR 116’s real head branch
- Incorporate current main
- Resolve the conflicts
- Commit the resolved result to the actual PR branch
- Leave the PR open and unmerged
- Report the final GitHub-visible PR URL, branch-head SHA, main SHA incorporated, conflicts resolved, and validation results
Additional information
Possibly related:
What issue are you seeing?
Product/Area:
ChatGPT Work / Codex / GitHub connector
Severity:
High
Summary:
Codex using the 5.6 model path repeatedly failed to complete a real GitHub PR branch update, claiming the environment did not have the capability to access or update the actual PR branch. The same task was then run with the 5.5 model path and succeeded using the GitHub connector.
This suggests the GitHub connector, repository permissions, and user-side authentication are valid, and the failure is specific to 5.6’s tool discovery, connector routing, branch-write reasoning, or capability detection.
Repository:
thochaos/madison-pm-deploy
Affected PR:
PR 116
Task requested:
Resolve conflicts on the actual GitHub branch for PR 116 against current main. Do not merge or deploy.
Conflicted files reported by GitHub:
Actual behaviour under 5.6:
Multiple 5.6 runs failed or stopped, reporting that the environment could not update the actual GitHub branch or lacked real GitHub branch-write capability. The failures implied the task could only be done locally or not at all.
This was incorrect.
Actual behaviour under 5.5:
The same class of task was run under 5.5 and succeeded.
5.5 was able to:
Successful final result from 5.5:
PR: https://github.com/thochaos/madison-pm-deploy/pull/116
Final PR branch head:
de9e97f83856e07b147154da4e52135ec604e840
Current main incorporated:
b1679359d6be488462335dd6da70b7e450e0fdaf
GitHub state after 5.5 run:
Why this matters:
This appears to rule out:
The same connector and repository access worked under 5.5. The blocker appears specific to the 5.6 Work/Codex model path.
Suspected issue:
5.6 may be failing in one or more of these areas:
Requested investigation:
Please investigate why Codex 5.6 failed to use available GitHub connector capabilities that Codex 5.5 successfully used for the same repository, PR, and branch-update workflow.
What steps can reproduce the bug?
Open ChatGPT Work/Codex using the 5.6 model path.
Use a workspace with the GitHub connector installed and connected to a repository where the connector has branch write access.
Ask Codex to update an actual GitHub PR branch, not a local-only branch. In my case:
Repository: thochaos/madison-pm-deploy
PR: 116
Task: resolve conflicts against current main, commit the result to the real PR branch, and do not merge or deploy.
Include instructions that local git clone/fetch/auth failure should not be treated as a blocker if the GitHub connector can read and write the actual branch.
Observe that Codex 5.6 fails or stops, claiming it cannot access/update the real PR branch or that only local changes are possible.
Repeat the same task using the 5.5 model path.
Observe that 5.5 successfully uses the GitHub connector, detects branch write access, reads the PR metadata, updates the actual PR branch, and reports the GitHub-visible final branch head SHA.
What is the expected behavior?
Expected behaviour:
Codex should use the available GitHub connector to:
Additional information
Possibly related: