Insiders Feedback: Pop-ups are never satisfied

オープン
#3,533 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 2 日以内に返信

まだ誰も着手していません。

評価

難易度
4/5
見積もり時間
3〜5日
初心者へのやさしさ
44/100
issue の種類
バグ
明瞭さ
おおむね明確
活発さ
活発
技術スタック
github, go

調査の方向性

Start by locating the MCP approval pop-up implementation and its related tests in the repository; the issue does not name specific files or tests. Reproduce the reported behavior in the VS Code Copilot chat flow, including pressing a button and revisiting chat history. Done means approval completes after a choice and the dialog no longer prompts again.

索引モデルが issue の本文から書いたものです。

説明

Version: Insiders

Feature: MCP's pop-up to create a PR ... or amend or a PR, or any "can we do this?" prompt.

Feedback:

TL;DR: We've all heard of someone "not taking NO for an answer": Well, this MCP seems unwilling to accept "yes" as a final answer too.

I'm using Visual Studio Code's github copilot extension and this MCP update has scuppered productivity.
It'll display a (poorly-dimensioned!) dialog within the chat window (making it hard to see what's going on) and if you do "press the button", nothing proceeds - the AI just hangs, like it's still waiting.
Also, sometimes the dialog doesn't appear at all - you just get a blank space in the CoPilot chat area, and you have to scroll it off the screen and back again before it'll render.

Worse, if you later scroll back up to see your history to see what happened, up pops the MCP dialog again within the chat history, asking you to do it again!

Image

AFAICT it "doesn't notice" when you push the JDFI button (e.g. "Update pull request" in the screenshot, but "Create" also behaves the same way) and seems to tell the AI "the human hasn't answered yet" (causing progress to stop), and does so even after the human has pressed "yes".

What I'd expect it to do is to grey-out the "Update pull request" button once it's been pressed. I'd also expect there to be a "Hell no you don't! Cancel that!" button too, which should be similarly "sticky" in that, once selected, it should stay selected.
i.e. a "done" dialog should turn into a read-only rendition of what was done, rather than remaining an interactive demand for approval.

PS an effective workaround is to instruct the AI to use the gh command-line instead of the MCP but that's not as visually appealing as this new feature could be.

主要言語
Go
スター
34.4k
フォーク
5.3k
平均マージ
3日 10時間
マージ済み PR(30日)
11

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

github/github-mcp-server のほかの issue

github/github-mcp-server の issue をすべて見る

似ている issue

Go の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。