github / github/copilot-cli

Copilot Cloud Agent gets intermittent access denied errors

Abierto
#3,041 1 comentario 6 reacciones 0 asignados Ver en GitHub
area:authentication area:tools
Lenguaje dominante
Shell
Estrellas
11.2k
Forks
1.9k
Merge medio
14 h 16 min
PR fusionados (30 d)
6

Descripción

### Describe the bug

We are using copilot coding agent mode for working on github issues and have instructed copilot to use the report_progress tool to push files to remote since github cli (git push command gets a 'The push failed due to access permissions') and github api (gets 'The GITHUB_TOKEN doesn't have write access via git push or the git API') both get an error.

Although the report_progress seems to work most of the times, it shows following intermittent issues:

Copilot report_progress tool gets access denied error "remote: Write access to repository not granted.fatal: unable to access 'https://github.com/...': The requested URL returned error: 403" randomly even though it has pushed successfully in the same session earlier, where it had got a "Progress reported successfully." result after invoking the tool.

We have also tried instructing copilot to use just the github_mcp_server/push_files tool, but that has below issues:
a. Despite clear instruction to not use the report_progress tool, copilot will still attempt to use it (and may succeed which causes another issue as below)
b. Later, it may use the github_mcp_server/push_files but that leads to git rebase errors as there seem to be two users it users that do the push via report_progress Vs github_mcp_server/push_files

Could you pl advise on how to avoid intermittent access denied errors

Thanks

### Affected version

Multiple versions of cloud agent

### Steps to reproduce the behavior

_No response_

### Expected behavior

Should not get access denied error and be able to push code successfully

### Additional context

_No response_

Guía de contribución

Abrir la guía de contribución

Línea de trabajo

Start by comparing the report_progress and github_mcp_server/push_files paths described in the issue, including how each authenticates and pushes changes. Reproduce the cloud agent workflow and capture when the 403 or rebase error occurs; done means both push methods behave consistently without access-denied or conflicting-push failures.

Escrito por el modelo de indexación a partir del texto del issue.

Evaluación

Stack tecnológico
git, github
Área
developer-experience, tooling
Tipo de issue
Error
Dificultad
4/5
Tiempo estimado
3-5 días
Estado de actividad
Tranquilo
Claridad
Necesita aclaración
Aptitud para principiantes
42/100

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.