Insiders Feedback: Pop-ups are never satisfied

Offen
#3,533 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 2 Tagen

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Anfängerfreundlichkeit
44/100
Issue-Typ
Bug
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
github, go

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

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.

Vorherrschende Sprache
Go
Sterne
34.4k
Forks
5.3k
Ø Merge
3 T. 10 Std.
Gemergte PRs (30 T.)
11

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus github/github-mcp-server

Alle Issues in github/github-mcp-server

Ähnliche Issues

Weitere Issues zu Go

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.