{"version":"2.1.305","anchor":"hooks-modules-are-refused-in-a-tool-servers-daemon","canonical_anchor":"hooks-modules-are-refused-in-a-tool-servers-daemon","heading":"Hooks modules no longer load inside a tool server's background process","tier":"notice","area":"Hooks","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305\/e\/hooks-modules-are-refused-in-a-tool-servers-daemon","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305","markdown":"### Hooks modules no longer load inside a tool server's background process\n\nClaude Code refuses to load hooks modules when running as a tool server's daemon, which can hold your token and runs shell commands\n\n**What**\n\nA hooks module is code that Claude Code can load to run at set points. A daemon is a background process, here one that serves tools to another program. Claude Code now refuses to load any hooks module when it is running as a tool server's daemon, because that process can hold your sign-in token and runs its caller's shell commands.\n\n**Why**\n\nThis closes a way for hooks modules supplied by a plugin to run inside a process that holds your credentials.\n\n- Area: Hooks\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: yes"}