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
-
難度 2/5 1-3 小時 新手友好度 75/100
eclipse-theia/theia#18098 ·
維護者通常 4 天內回覆
-
area/sessions comp/tui needs-repro P2 sweeper:risk-session-state type/bug
難度 2/5 1-3 小時 新手友好度 74/100
NousResearch/hermes-agent#127449 · 1 則留言 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 85/100
Mintplex-Labs/anything-llm#6537 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 88/100
rohitg00/agentmemory#1435 ·
維護者通常 3 天內回覆
-
難度 2/5 1-3 小時 新手友好度 84/100
WingedGuardian/GENesis-AGI#2543 ·
維護者通常 1 天內回覆