ask_user marks an active app user unavailable, then continues with other actions
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
Research direction
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.
Written by the indexing model from the issue text.
Description
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
- Dominant language
- No language data
- Stars
- 2.1k
- Forks
- 157
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from github/app
-
triage
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
When using GPT-5. Open
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Similar issues
-
area-ai untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
dotnet/extensions#7783 ·
-
comp/agent P2 provider/kimi provider/openrouter type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
NousResearch/hermes-agent#122303 · 1 comment ·
-
samples
Difficulty 1/5 Under an hour Newbie friendliness 92/100
-
sdk-python
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
anomalyco/models.dev#8058 · 1 comment ·