Skip to content

Insiders Feedback: Issue creation widget in VS Code Copilot Chat usability #2602

Open

Description

@easyt

Version: Insiders

Feature: Issue creation widget in VS Code Copilot Chat

Feedback:
I love this feature. This is way better than looking at JSON.

Two issues:

  1. When bypassing approvals, the widget still shows even though the agent creates the issue later on in the chat. This can lead to duplicate issue creation if you edit the text in the widget and submit it again, not realizing the agent has already auto-created the issue.
  2. After submitting, I moved on to other work, then came back to a disconnected codespace. After reconnecting, the chat rendered with the widget as if I never submitted the new issue to be created, even though it was already created.

Screenshot: taken after reconnecting to codespace, showing the widget as if issue was never submitted (even though it was)

Reference: https://modelcontextprotocol.io/extensions/apps/overview

View original Slack conversation

Activity

  1. mattdholloway commented on Jun 16, 2026

    @mattdholloway
    Contributor

    This is a very interesting point - some kind of persistent state on reloads would be fantastic. I'm thinking of ways that this could be ensured across different clients.

  2. added
    insidersFeatures for the Insiders mode of the GitHub MCP Server
    on Jun 24, 2026
  3. Omzig commented on Oct 22, 2026

    @Omzig

    I hit a related duplicate-creation path through an MCP client:

    1. Calling an interactive GitHub create tool opens a form; the tool response tells the caller to wait for the user to submit it.
    2. After submission, the client can surface a new call_tool request with _ui_submitted: true instead of returning the result of the original invocation.
    3. If the agent treats that as a request to call the create tool again, another form opens. Submitting both can create duplicate issues. I have hit this and created duplicate issues.

    Expected: submitting the form should resolve the original pending tool call with its result, or submissions/retries should be correlated and idempotent so the agent cannot accidentally open a second create form.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

insidersFeatures for the Insiders mode of the GitHub MCP Server

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions