{"version":"2.1.319","anchor":"deferred-tool-tracking-made-unconditional","canonical_anchor":"deferred-tool-tracking-made-unconditional","heading":"Tool-use tracking no longer depends on a feature check","tier":"internal","area":"Tools","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319\/e\/deferred-tool-tracking-made-unconditional","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319","markdown":"### Tool-use tracking no longer depends on a feature check\n\nClaude Code now always records which tools a conversation used, and fills in that list when a conversation is moved\n\n**Unclear.** The feature check may have moved somewhere else rather than been removed, so whether this tracking runs for every user is not known.\n\n**What**\n\nClaude Code keeps track of which tools a conversation has used. Before, this tracking only ran when a feature check passed. That check is no longer there, so the tracking always runs.\n\nWhen a conversation is moved, Claude Code now also fills in the list of tools it had used and sends a usage record saying it did.\n\n**Why**\n\nIn practice, this concerns the tools that Claude Code loads only when they are needed, rather than having them all ready from the start.\n\n- Area: Tools\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}