What probably matters to youSection of the release
What
A plugin's hooks module, a code file that runs at set moments, can now respond to a new tool.list event. Through it, the module can:
remove tools from the session
add new tools, each with a name, a description and a description of the input it takes
An added tool needs a tool.call hook to answer when Claude uses it. Without one, the call fails with a message saying no tool.call hook answered.
Claude Code refuses, with a warning, any added tool whose name matches an existing tool or starts with mcp__. If handling the event takes longer than its time limit, it keeps running behind later events.
Why
Plugin authors can now shape the set of tools Claude has in a session, not just react to tool use.