Skip to content

Fix MCP status drift after auth/restart/reload#47

Open
adityakulraj wants to merge 2 commits intosamhu1:masterfrom
adityakulraj:feature/adkunwar-issue-38-mcp-status-drift-clean
Open

Fix MCP status drift after auth/restart/reload#47
adityakulraj wants to merge 2 commits intosamhu1:masterfrom
adityakulraj:feature/adkunwar-issue-38-mcp-status-drift-clean

Conversation

@adityakulraj
Copy link
Copy Markdown
Contributor

Summary

  • normalize MCP status mapping in runtime and workspace hooks
  • always apply MCP status responses (including empty server lists) so removed/disconnected servers clear correctly
  • preserve MCP error details when mapping statuses
  • avoid falling back to draft statuses for live sessions, preventing stale status leakage

Validation

  • confirmed no remaining guarded status updates (result.servers?.length / statusResult.servers?.length) in the updated hooks
  • could not run project build locally because pnpm is unavailable in this environment and corepack pnpm fails due to TLS certificate verification

Closes #38

@adityakulraj adityakulraj requested a review from samhu1 as a code owner March 24, 2026 07:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Fix MCP server status drift after auth, restart, and reload flows

1 participant