Insiders Feedback: In-Chat UI Form

Aberta
  • Algo errado?
#3,641 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
5/5
Tempo estimado
Mais de uma semana
Facilidade para iniciantes
12/100
Tipo de issue
Bug
Clareza
Precisa de esclarecimento
Status de atividade
Ativa
Stack de tecnologia
go, vscode
Domínio
ai

Direção de pesquisa

The payload names no source files, so start by finding where the in-chat form is raised and how its submission returns to the agent turn, then reproduce it with VSCode Insiders on an issue create or update. Done would mean a submitted form resumes the turn with the result visible to the agent, a form is not shown again after approval, and an update form includes the existing issue title. The report mixes several separate problems, so the scope needs narrowing with a maintainer first.

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

Descrição

bug insiders user-experience

Version: Insiders

Feature: In-Chat UI Form

Feedback:
This has started appearing for me on things like issue create and update. It does give a nicer view of what the result will be but it is so far a really poor experience for working with the agent.

Showing the form stops the agent in its tracks and even when submitted the agent doesn't resume so I have to ask it to continue. The agent was then not aware the issue had been created successfully and told me it hadn't been so it ended up being duplicated when I pressed Submit again.

The overall experience is a massive downgrade on how it was working previously as my main priority is that the agent can complete its tasks with minimal interruption and certainly not something that prematurely ends the turn.

I also had an incomplete UI form appear for an issue update (it was missing the existing issue title) so I couldn't even press submit without manually editing.

The forms also keep reappearing in the VSCode chat for approval despite having already been approved.

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.