{"version":"2.1.265","anchor":"late-tool-additions-rejection-message-now-also-mentions-inli","canonical_anchor":"late-tool-additions-rejection-message-now-also-mentions-inli","heading":"late-tool-additions rejection message now also mentions inline-tools fallback","tier":"internal","area":"Tool Search","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265\/e\/late-tool-additions-rejection-message-now-also-mentions-inli","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265","markdown":"### late-tool-additions rejection message now also mentions inline-tools fallback\n\nRejected late-tool-addition warning now also mentions falling back to inline tools\n\n**What**\n\nWhen Claude Code rejects a late addition of a tool-related beta feature, the warning it logs now also notes that, if there's no ToolSearch feature available, the fallback is to inline tools instead. Previously the message only mentioned falling back to the ToolSearch announcement. The rejection still stays in effect ('sticky') until `\/clear` or `\/compact` is run.\n\n**Why**\n\nThis makes the internal warning more accurate about what actually happens when a late tool addition is rejected, which is useful context for anyone diagnosing why tools behave differently until the conversation is cleared or compacted.\n\n- Area: Tool Search\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}