You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Insiders Feedback: Create issue MCP app shows up again for alreay created issues #3873
Looks like the agent doesn't know that I already have created the issue in step 2:
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"
}
Activity
aeschli commentedon Nov 17, 2026
Looks like the agent doesn't know that I already have created the issue in step 2:
Input:
aeschli commentedon Nov 17, 2026
If this is a VS Code issue, please let me know (assign to @connor4312 )