Insiders Feedback: In-Chat UI Form
維護者通常 2 天內回覆
還沒有人認領這個 Issue。
評估
研究方向
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.
由索引模型根據 Issue 內容生成。
描述
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.
- 主要語言
- Go
- 星號
- 34.2k
- 分支
- 5.3k
- 平均合併
- 5 天 18 小時
- 30 天內合併 PR
- 13
環境準備
- 提供 Dockerfile 或 Docker Compose 檔案
- 有 Pull Request 範本
- 閱讀貢獻指南
從這裡開始
- 先讀完整個 Issue，再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫，在一個分支上完成修改。
- 送出 Pull Request，並在描述裡引用這個 Issue 編號。
github/github-mcp-server 的其他 Issue
-
難度 2/5 1-3 小時 新手友好度 69/100
github/github-mcp-server#3760 ·
維護者通常 2 天內回覆
-
難度 2/5 1-3 小時 新手友好度 82/100
github/github-mcp-server#3758 ·
維護者通常 2 天內回覆
-
難度 2/5 1-3 小時 新手友好度 69/100
github/github-mcp-server#3729 ·
維護者通常 2 天內回覆
-
難度 2/5 1-3 小時 新手友好度 65/100
github/github-mcp-server#3722 ·
維護者通常 2 天內回覆
-
Insiders Feedback: PR created UI doesn't link to the PR可能已有人在做 @genius-0963 於 5 天前認領。 未關閉bug insiders user-experience
難度 2/5 1-3 小時 新手友好度 65/100
github/github-mcp-server#3658 ·
維護者通常 2 天內回覆
查看 github/github-mcp-server 的全部 Issue
相似的 Issue
-
ready-for-agent
難度 2/5 1-3 小時 新手友好度 78/100
hexlet-basics/hexlet-basics#962 ·
維護者通常 1 天內回覆
-
imapproxy closeForMaintenance grace timer calls clientConn.Close() before closeMaintenanceTransport可能已有人在做 @dejanstrbac 今天認領。 未關閉
難度 2/5 1-3 小時 新手友好度 83/100
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 76/100
-
renovate-health
難度 2/5 1-3 小時 新手友好度 62/100
Netcracker/qubership-network-latency-exporter#267 ·
維護者通常 1 天內回覆
-
Network capture does not work可能已有人在做 @KSpaceer 今天認領。 未關閉kind/bug
難度 2/5 1-3 小時 新手友好度 82/100
aquasecurity/tracee#5395 ·