-
Notifications
You must be signed in to change notification settings - Fork 2.6k
fix(mcp): Revert changes causing startup issues and remove refresh notifications #6878
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
…le notifications - Reverted PR #6779 which prevented unnecessary MCP server refreshes but caused startup failures - Temporarily disabled MCP notification popups as a stopgap solution - Added TODO comments explaining the temporary nature of disabled notifications - This allows MCP servers to function properly while a more robust solution is developed
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for this PR! The revert approach is a pragmatic solution to fix the MCP startup issues. I've reviewed the changes and have some suggestions for improvement.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.
Description
This PR reverts the optimization that caused MCP servers to fail on startup and permanently removes the MCP refresh info notifications from the extension logic. The UI already provides a green indicator for MCP status, so duplicative VS Code popups are unnecessary.
Problem
PR #6779 introduced an optimization to avoid unnecessary MCP server refreshes on settings save, which led to MCP servers failing on startup.
Solution
Revert the problematic change from PR fix: prevent unnecessary MCP server refresh on settings save (#6772) #6779 to restore stable MCP startup.
Remove all VS Code information notifications related to MCP refresh in the backend:
The UI status indicator remains the single source of truth for user feedback.
Restore test coverage for the webview message handler MCP toggle path to prevent regressions.
Changes Made
Rationale
Testing
Checklist