ask_user marks an active app user unavailable, then continues with other actions
まだ誰も着手していません。
評価
調査の方向性
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 にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
github/app のほかの issue
-
triage
難易度 2/5 1〜3時間 初心者へのやさしさ 70/100
-
難易度 2/5 1〜3時間 初心者へのやさしさ 65/100
-
When using GPT-5. オープン
難易度 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 件 ·