{"version":"2.1.248","anchor":"turning-off-large-mcp-output-files-now-requires-an-exact-val","canonical_anchor":"turning-off-large-mcp-output-files-now-requires-an-exact-val","heading":"Turning off large MCP output files now requires an exact value","tier":"use","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/turning-off-large-mcp-output-files-now-requires-an-exact-val","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Turning off large MCP output files now requires an exact value\n\nOnly an exact false now disables large MCP output files; other values no longer switch it off.\n\n**What**\n\n`ENABLE_MCP_LARGE_OUTPUT_FILES` is now compared strictly against false rather than parsed for truthiness, so only a value that reads as exactly false disables persisting oversized MCP results and forces truncation instead. Other values no longer accidentally switch it off.\n\n**Details**\n\n- The telemetry reason string for the disabled case is unchanged.\n\n**Evidence**\n\n`env_disabled`\n\n- Area: MCP\n- Names: `ENABLE_MCP_LARGE_OUTPUT_FILES`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 2\/5"}