{"version":"2.1.267","anchor":"bug-fix-sigint-cleanup-guard-flag-was-setting-the-wrong-var","canonical_anchor":"bug-fix-sigint-cleanup-guard-flag-was-setting-the-wrong-var","heading":"Bug fix: SIGINT cleanup guard flag was setting the wrong variable","tier":"notice","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267\/e\/bug-fix-sigint-cleanup-guard-flag-was-setting-the-wrong-var","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267","markdown":"### Bug fix: SIGINT cleanup guard flag was setting the wrong variable\n\nFixed a bug where Ctrl-C cleanup for MCP servers checked one variable but set a different one\n\n**What**\n\nWhen Claude Code handles Ctrl-C (SIGINT) to shut down MCP servers, the cleanup code used a guard flag to prevent the cleanup from running twice. Due to a bug, it checked one variable but set a different, unrelated one, so the guard never actually took effect. It now correctly sets the same flag it checks.\n\n**Why**\n\nThis fixes a bug that could have allowed MCP server cleanup on Ctrl-C to run more than once instead of being properly guarded against double execution.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}