Skip to content

Insiders Feedback: Create issue MCP app shows up again for alreay created issues #3873

Backlog

Description

@aeschli

Version: 1.147.0-insider
Commit: 95906867e0763b595ee0c8814ba93fea96798d3e
Date: 2026-11-16T04:29:26Z (1 day ago)

@github/copilot: 1.0.111-0
@github/copilot-sdk: 1.0.33-preview.0

  • ask the agent to create an issue
  • it will open a Create issue MCP app inside that. Create the issue from there.
  • now ask it to make an update to the issse
    🐛 the 'Create issue' is back
Screenshot 2026-11-17 at 11 23 18

Activity

  1. aeschli commented on Nov 17, 2026

    @aeschli
    Author

    Looks like the agent doesn't know that I already have created the issue in step 2:

    Screenshot 2026-11-17 at 11 28 53

    Input:

    {
      "body": "## Issue\n\nHook error messages shown to users are confusing and unhelpful. The current error message lacks context about what actually failed.\n\n### Current behavior\n\nWhen a plugin hook fails in the session sandbox, users see:\n\n```\nError: (hook) postToolUse hook from \"review-plan@vscode-team-kit\" failed in the session sandbox: Hook command failed with code 1. Stderr omitted for privacy. If it needs more access, allow it in the sandbox policy.\n```\n\n### Problems with this error message\n\n1. **Generic error code** - \"code 1\" doesn't tell the user what went wrong\n2. **Missing context** - No indication of what the hook was trying to do\n3. **Misleading privacy note** - \"Stderr omitted for privacy\" suggests the user can fix this by changing policies, but that's not necessarily true\n4. **Unclear action** - \"allow it in the sandbox policy\" is vague and doesn't explain what needs to be allowed or why\n\n### Steps to reproduce\n\n1. Install the review-plan plugin: `/plugin install review-plan@vscode-team-kit`\n2. Enable the plugin in the customizations UI\n3. Make an LLM request in a chat session\n4. The postToolUse hook from review-plan will fail with the confusing error message\n\n### What the hook does\n\nThe review-plan postToolUse hook reads from stdin, parses tool events, and checks if any edits touch a `plan.md` file. If so, it outputs additional context instructing to use the `review-plan` skill to review the plan. The hook is likely failing because it needs stdin access in the sandbox environment, which makes the error message even more critical — users need to know \"this hook needs stdin access\" rather than just \"code 1\".\n\n### Suggested improvements\n\n- Include the actual error message or at least a meaningful error category\n- Explain what the hook was attempting to do\n- If the error is a sandbox access issue, be specific about what resource/permission is needed (e.g., \"needs access to stdin\")\n- If the error is from the hook itself, suggest debugging steps (e.g., check plugin logs)\n- Consider different error messages for different failure modes (timeout, permission, crash, etc.)\n\n### Context\n\nThis was discovered while testing team-managed plugin customizations (#343845).",
      "labels": [
        "chat",
        "ai-customizations"
      ],
      "method": "create",
      "owner": "microsoft",
      "repo": "vscode",
      "title": "Improve hook error messages in plugin sandbox"
    }
    
  2. aeschli commented on Nov 17, 2026

    @aeschli
    Author

    If this is a VS Code issue, please let me know (assign to @connor4312 )

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions