Insiders Feedback: In-Chat UI Form
Maintainers usually reply within 2 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 12/100
Research direction
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.
Written by the indexing model from the issue text.
Description
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.
- Dominant language
- Go
- Stars
- 34.2k
- Forks
- 5.3k
- Avg merge
- 5d 18h
- Merged PRs (30d)
- 13
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from github/github-mcp-server
-
Difficulty 2/5 1-3 hours Newbie friendliness 69/100
github/github-mcp-server#3760 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
github/github-mcp-server#3758 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 69/100
github/github-mcp-server#3729 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
github/github-mcp-server#3722 ·
Maintainers usually reply within 2 days
-
Insiders Feedback: PR created UI doesn't link to the PRPossibly taken @genius-0963 claimed this 5 days ago. Openbug insiders user-experience
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
github/github-mcp-server#3658 ·
Maintainers usually reply within 2 days
All issues in github/github-mcp-server
Similar issues
-
ready-for-agent
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
hexlet-basics/hexlet-basics#962 ·
Maintainers usually reply within 1 day
-
imapproxy closeForMaintenance grace timer calls clientConn.Close() before closeMaintenanceTransportPossibly taken @dejanstrbac claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
renovate-health
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Netcracker/qubership-network-latency-exporter#267 ·
Maintainers usually reply within 1 day
-
Network capture does not workPossibly taken @KSpaceer claimed this today. Openkind/bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
aquasecurity/tracee#5395 ·