Insiders Feedback: In-Chat UI Form

Abierto
  • ¿Algo no está bien?
#3,641 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 2 días

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
12/100
Tipo de issue
Error
Claridad
Necesita aclaración
Estado de actividad
Activo
Stack tecnológico
go, vscode
Área
ai

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.

Lenguaje dominante
Go
Estrellas
34.2k
Forks
5.3k
Merge medio
5 d 18 h
PR fusionados (30 d)
13

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de github/github-mcp-server

Todos los issues de github/github-mcp-server

Issues similares

Más issues de Go

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.