Insiders Feedback: In-Chat UI Form

Ouverte
  • Quelque chose ne va pas ?
#3,641 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 2 jours

Personne n'a encore pris cette issue.

Évaluation

Difficulté
5/5
Temps estimé
Plus d'une semaine
Accessibilité débutants
12/100
Type d'issue
Bug
Clarté
À clarifier
Activité
Active
Stack technique
go, vscode
Domaine
ai

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

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.

Langage dominant
Go
Étoiles
34.2k
Forks
5.3k
Merge moyen
5 j 18 h
PR mergées (30 j)
13

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de github/github-mcp-server

Toutes les issues de github/github-mcp-server

Issues similaires

Plus d'issues Go

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.