{"version":"2.1.248","anchor":"ide-code-execution-and-diagnostics-tools-listed-by-name","canonical_anchor":"ide-code-execution-and-diagnostics-tools-listed-by-name","heading":"IDE code execution and diagnostics tools listed by name","tier":"internal","area":"IDE Integration","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/ide-code-execution-and-diagnostics-tools-listed-by-name","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### IDE code execution and diagnostics tools listed by name\n\nTwo IDE tools for running code and reading diagnostics are now named constants for special-casing.\n\n**What**\n\nTwo separate lists now name `mcp__ide__executeCode` and `mcp__ide__getDiagnostics` as real constants where previously there were no-op placeholders, so these two IDE tools are special-cased somewhere in permission or tool-filtering.\n\n**Evidence**\n\n`[\"mcp__ide__executeCode\", \"mcp__ide__getDiagnostics\"]`\n\n- Area: IDE Integration\n- Names: `mcp__ide__executeCode`, `mcp__ide__getDiagnostics`\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5"}