{"version":"2.1.280","anchor":"tools-have-updated-definitions-notice-for-deferred-tool-sc","canonical_anchor":"tools-have-updated-definitions-notice-for-deferred-tool-sc","heading":"Tool-change notices now distinguish replaced tools from added or removed ones","tier":"notice","area":"Tool Listing","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/tools-have-updated-definitions-notice-for-deferred-tool-sc","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### Tool-change notices now distinguish replaced tools from added or removed ones\n\nClaude Code now tells you when a tool's definition was replaced, not just added or removed\n\n**What**\n\n- Claude Code now separately tracks tools whose definition (schema) was replaced, instead of lumping them in with tools that were simply added or removed. This is tracked internally as `replacedNames`.\n\n- A new notice, 'tools have updated definitions', appears when a tool you already had access to gets a new schema pushed to it.\n\n- A new transcript entry type (`tool_hosts_correction`) and new reminder text groupings (such as 'the following tools were replaced') support this distinction in the session transcript.\n\n**Why**\n\nPreviously, replacing a tool's definition looked the same as adding or removing a tool, which could be confusing when reading back what happened in a session. Now the notices are more precise about what actually changed.\n\n- Area: Tool Listing\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}