{"version":"2.1.323","anchor":"tool-list-now-rebuilt-through-a-toollist-hook-mechanism","canonical_anchor":"tool-list-now-rebuilt-through-a-toollist-hook-mechanism","heading":"The list of available tools can now be rebuilt when plugins signal a change","tier":"notice","area":"Plugin Hooks","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/tool-list-now-rebuilt-through-a-toollist-hook-mechanism","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### The list of available tools can now be rebuilt when plugins signal a change\n\nClaude Code can now rebuild its list of available tools in response to a `tool.list` event, so the list can change during a session\n\n**Unclear.** It is not clear whether this is active for everyone or only behind a plugin setting that is switched on separately.\n\n**What**\n\nClaude Code keeps a list of the tools Claude may use, such as reading files or running commands. It can now rebuild that list when a `tool.list` event fires. Each rebuild bumps a revision number, so Claude Code stops reusing the old saved copy of the list and picks up the new one.\n\n**Why**\n\nThis appears to let plugin modules add to or change the tool list while a session is running, instead of the list being fixed once at the start.\n\n- Area: Plugin Hooks\n- Names: `tool.list`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}