Insiders Feedback: Pop-ups are never satisfied

Aberta
#3,533 0 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 2 dias

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
4/5
Tempo estimado
3-5 dias
Facilidade para iniciantes
44/100
Tipo de issue
Bug
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
github, go

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

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.

Linguagem predominante
Go
Estrelas
34.4k
Forks
5.3k
Merge médio
3d 10h
PRs com merge (30d)
11

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de github/github-mcp-server

Todas as issues de github/github-mcp-server

Issues semelhantes

Mais issues de Go

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.