A clear path forward
Why can Agent read my GitHub repository but not push or open a PR?
Check the connection and write permissions used for the failed action. Being able to list or read a GitHub repo does not prove that the same action can push a branch or open a pull request, or PR.
Personal and shared connections can have different access. GitHub's repository rules also still apply when Agent works on your behalf.
- Keep the exact error and note whether the failure was a push, PR creation or a change to a protected file.
- Open Repos in the affected workspace and check the GitHub connection used for that action.
- Confirm that it covers the intended repository and has the needed write access. If a shared App grant is involved, your GitHub admin may need to approve a change.
- Retry after the specific access or sign-in problem is corrected. Check that the branch or PR was actually created.
Do not turn off branch protection or remove every connection as a general fix. A working read and a failed write are useful clues; keep both results when investigating the cause.
Was this page helpful?
Still stuck? Try troubleshooting with Agent.
Still stuck? Try troubleshooting with Agent.
Copy this prompt and paste it into Agent. For a project issue, open the project where it happens first. Add what happened and anything you've already tried. Don't include passwords, API keys, database connection strings or payment-card details.
Copying does not open Agent or send a support request. Agent availability and usage depend on your account.
Can't open your project, or need another kind of help? Get help.