Claude Code opens its interface and tool calls to user-written mods

A team could add a pane showing a build's status, replace a built-in feature, or require an extra check before a deployment. The useful change is that the surrounding software becomes adaptable alongside the prompts given to the model.

The official documentation requires version 2.1.287 or later. Mods arrive as plugins and can observe an event, alter it, or answer in place of the normal behavior. Their visual additions appear in the terminal and the Desktop app's Code tab; other supported environments can run the hooks without showing the interface.[2]

That control carries a concrete boundary: mods are not sandboxed. They run with the user's access to files, processes and the network. On managed machines and Team or Enterprise accounts, a built-in guard protects organizational settings and managed instructions. By default where that guard loads, a mod cannot overturn a denied Claude tool call. But this does not prevent the mod's own code from reading a file or starting a process the user could access.[3]

Before installing one, read its source and use the documented validation command to inspect its hooks and API calls. Organizations can restrict loading to managed mods.[3] Treat the change as an opportunity to make a familiar tool fit a particular practice, with review of the extension itself; the announcement does not establish that every community mod is dependable.