{"version":"2.1.269","anchor":"new-restored-tool-category-tracked-in-deferred-tools-pool","canonical_anchor":"retracted-tool-restoration-now-gets-its-own-explicit-availa","heading":"Tools that become available again after being hidden are now tracked and announced explicitly","tier":"notice","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269\/e\/new-restored-tool-category-tracked-in-deferred-tools-pool","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269","markdown":"### Tools that become available again after being hidden are now tracked and announced explicitly\n\nTools that come back after being hidden or retracted are now tracked as a distinct \"restored\" group and get their own message to the model\n\n**What**\n\n- The logic that tracks changes to the pool of deferred tools (tools not immediately shown to the model) now identifies a new \"restored\" category: tools that are currently announced, still allowed, and no longer hidden. These are reported as `restoredCount`\/`restoredNames` in the tracking event, and also used elsewhere to un-hide tools that had been hidden.\n\n- When tools that were previously retracted (the model had been told to disregard them) become available again, the transcript now gets a dedicated message telling the model that the earlier \"disregard this tool\" instruction no longer applies, separate from the general re-available-tools note.\n\n**Why**\n\nThis makes sure the model is clearly told when a tool it was instructed to ignore is usable again, instead of relying on a generic message that might not make that clear.\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}