ask_user marks an active app user unavailable, then continues with other actions
还没有人认领这个 Issue。
评估
调研方向
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.
由索引模型根据 Issue 内容生成。
描述
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
- 主要语言
- 没有语言数据
- 星标
- 2.1k
- 派生
- 157
- PR 合并指标
- 30 天内没有已合并 PR
贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
github/app 的其他 Issue
-
triage
难度 2/5 1-3 小时 新手友好度 70/100
-
难度 2/5 1-3 小时 新手友好度 65/100
-
难度 2/5 1-3 小时 新手友好度 70/100
-
难度 2/5 1-3 小时 新手友好度 70/100
-
难度 2/5 1-3 小时 新手友好度 70/100
相似的 Issue
-
area-ai untriaged
难度 2/5 1-3 小时 新手友好度 78/100
dotnet/extensions#7783 ·
-
comp/agent P2 provider/kimi provider/openrouter type/bug
难度 2/5 1-3 小时 新手友好度 78/100
NousResearch/hermes-agent#122303 · 1 条评论 ·
-
samples
难度 1/5 1 小时以内 新手友好度 92/100
-
sdk-python
难度 2/5 1-3 小时 新手友好度 75/100
-
难度 2/5 1-3 小时 新手友好度 72/100
anomalyco/models.dev#8058 · 1 条评论 ·