{"version":"2.1.296","anchor":"synced-plugin-skill-hooks-removal-and-refusal-logging","canonical_anchor":"synced-plugin-skill-hooks-removal-and-refusal-logging","heading":"Synced plugin skills can lose their hooks, with a logged reason","tier":"notice","area":"Plugins","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296\/e\/synced-plugin-skill-hooks-removal-and-refusal-logging","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296","markdown":"### Synced plugin skills can lose their hooks, with a logged reason\n\nClaude Code can remove hooks from synced plugin skills, and records why a plugin skill or command was refused or run without its hooks\n\n**Unclear.** It is not stated what turns plugin sync on, so whether this applies to a given account is unknown.\n\n**What**\n\nSome plugins can be synced to your account, and their skills (reusable instructions Claude can call on) can bring hooks, which are commands that run automatically at set moments. Claude Code can now remove those hooks for these reasons:\n\n- plugin sync was turned off\n\n- the account changed\n\n- the skill is no longer there\n\nClaude Code also records when a plugin skill runs without its hooks or without its `allowed-tools` grant, and when a plugin command is not run. A skill whose plugin is not in your account's latest plugin list is refused.\n\n**Why**\n\nA synced plugin skill can lose its hooks or tool permissions without any visible sign. These records give a reason for it.\n\n- Area: Plugins\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: yes"}