Insiders Feedback:

Aberta
  • Algo errado?
#3,541 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
52/100
Tipo de issue
Bug
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
go
Domínio
tooling

Direção de pesquisa

Start by tracing the action tool call and its confirmation flow in the GitHub MCP Server; the issue does not name source files or tests. Reproduce PR creation in Copilot chat and follow what happens after Allow, including the second confirmation and whether the agent continues. Done means one approval creates the PR and the agent continues automatically.

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

Descrição

bug insiders user-experience 
Version: 1.140.0
Commit: 07f806f999227108933c2e30515b26eecc1fda74
Date: 2026-09-30T10:38:38+02:00
Electron: 43.7.3
ElectronBuildId: 15386805
Chromium: 150.0.7871.250
Node.js: 24.21.0
V8: 15.0.245.31-electron.0
@github/copilot: 1.0.89-7
@github/copilot-sdk: 1.0.15-preview.4
OS: Linux x64 7.0.0-38-generic
Feature: The UI component shown for action tool calls like PR create

Feedback:

I like the idea of an in-chat UI for action tool calls, but right now it conflicts with the normal flow. Here's what I see in Copilot chat:

  1. Tool calls aren't auto-approved, so the PR details are already visible in the confirmation prompt. The UI isn't great, but it's enough for a quick review of the PR create request. When I click Allow, the original tool call appears to be cancelled and shows an ✗ mark.

    Image

  2. A new UI then appears, asking me to confirm all the same details again. I have to approve a second time by clicking the Create PR button.

  3. Once that's done, the chat stops, and I have to ask the AI to continue. Previously, a single Allow was all it took and everything just worked.

Expected behavior: a single approval step, with the agent continuing automatically afterward.

Thanks for looking into this. I hope it gets resolved soon.

Linguagem predominante
Go
Estrelas
34.2k
Forks
5.3k
Merge médio
5d 18h
PRs com merge (30d)
13

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.