{"version":"2.1.321","anchor":"retry-telemetry-when-late-tool-additions-are-rejected","canonical_anchor":"retry-telemetry-when-late-tool-additions-are-rejected","heading":"Claude Code logs an extra report when tools added mid-conversation are rejected","tier":"internal","area":"Tools","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321\/e\/retry-telemetry-when-late-tool-additions-are-rejected","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321","markdown":"### Claude Code logs an extra report when tools added mid-conversation are rejected\n\nWhen tools added partway through a conversation are rejected, Claude Code can now record a retry report; the fallback you see is unchanged\n\n**What**\n\nClaude Code can add tools partway through a conversation. Sometimes those late additions are rejected. When that happens, Claude Code still falls back to announcing the tools through tool search, which is how Claude finds and loads tools that are held back until needed. That fallback has not changed.\n\nWhat is different is that, in some cases, Claude Code now also sends a usage report marking the rejection as a retry. Previously it only sent its existing report about the rejected addition.\n\n**Why**\n\nThe extra report hints that a retry path for rejected tool additions is being prepared. For now, nothing changes in what you see or in how the tools load.\n\n- Area: Tools\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}