{"version":"2.1.239","anchor":"warn-once-budgets-are-now-tracked-per-host-rather-than-per-p","canonical_anchor":"warn-once-budgets-are-now-tracked-per-host-rather-than-per-p","heading":"Warn-once budgets are now tracked per host rather than per process","tier":"internal","area":"Diagnostics","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239\/e\/warn-once-budgets-are-now-tracked-per-host-rather-than-per-p","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239","markdown":"### Warn-once budgets are now tracked per host rather than per process\n\nOne-time warnings are now tracked per host, so silencing one host does not silence the rest.\n\n**What**\n\nDozens of places that show a warning or log a diagnostic only once moved from a single process-wide registry to one scoped per host. In a single ordinary session nothing changes; in a process controlling several hosts, a warning silenced for one host no longer silences the others.\n\n**Details**\n\n- Affected sites include the tool-search decision log, the MCP tree diagnostic, the voice initialisation gate, cron task load failures, and the interface tree-depth cap.\n\n**Evidence**\n\n`tool_search_optimistic_decision`\n\n- Area: Diagnostics\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 3\/5"}