ask_user marks an active app user unavailable, then continues with other actions
Ninguém assumiu esta issue ainda.
Avaliação
- Dificuldade
- 4/5
- Tempo estimado
- 3-5 dias
- Facilidade para iniciantes
- 45/100
Direção de pesquisa
The issue is in the ask_user flow of the GitHub Copilot desktop app. Start by finding where ask_user is invoked and how the app determines user availability. Look at the activity log generation and the logic that auto-responds. Check the related issue #3606 for prior context. Testing will require reproducing the scenario in an active Windows session to see the fabricated response.
Escrita pelo modelo de indexação a partir do texto da issue.
Descrição
Short summary
The app displays an ask_user question, immediately answers it on the user's behalf with “The user is not available to respond,” and lets the agent continue with other actions even though the user is actively present in the app.
Affected version or release
GitHub Copilot app with Copilot CLI 1.0.87-0
Installation context
GitHub Copilot desktop app on Windows; active interactive session.
What happened?
While I was actively in the app, the agent asked me to complete a Microsoft device-login step. Instead of allowing me to answer, the app generated this response on my behalf:
The user is not available to respond and will review your work later. Work autonomously and make good decisions.
That availability claim is false: I was in the app at the time. The agent then moved on to other work rather than waiting for the requested input.
This is a recurrence of #3606, reported on September 7, 2026. The attached screenshot was captured on September 22, 2026, so the problem remains reproducible two weeks later. In this occurrence, the question is visible in the activity log before the fabricated unavailable response.
Steps to reproduce
- Open and actively use a session in the GitHub Copilot app.
- Have the agent reach a step that requires user input, such as device authentication.
- Let the agent invoke
ask_user. - Observe that the question appears in the activity log.
- Observe that the app immediately supplies an unavailable-user answer and the agent continues with unrelated work, without giving the active user a chance to respond.
Expected behavior
The app should present the question to the active user and pause for a response. It must not infer that the user is unavailable while they are actively using the session, and it must not continue past a blocked authentication or approval step based on a fabricated answer.
Additional context
Related report: #3606
- Linguagem predominante
- Sem dados de linguagem
- Estrelas
- 2.1k
- Forks
- 157
- Métricas de merge de PRs
- Nenhum PR com merge em 30d
Preparar o ambiente
Primeiros passos
- Leia a issue inteira e depois o guia de contribuição do projeto.
- Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
- Faça um fork do repositório e trabalhe em uma branch.
- Abra um pull request que referencie o número da issue.
Mais de github/app
-
triage
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 70/100
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 65/100
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 70/100
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 70/100
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 70/100
Issues semelhantes
-
bug
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 88/100
mrutunjay-kinagi/ragsearch#129 ·
Mantenedores costumam responder em até 1 dia
-
add latest sol modelAberta
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 68/100
netlify-labs/nax#56 · 2 comentários · 1 reação ·
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 78/100
msgbyte/dao-browser#64 ·
-
Dificuldade 1/5 Menos de uma hora Facilidade para iniciantes 88/100
Mantenedores costumam responder em até 2 dias
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 84/100
langchain-ai/langgraphjs#2916 ·
Mantenedores costumam responder em até 1 dia