{"version":"2.1.281","anchor":"plugin-hooksjson-accepts-a-schema-key","canonical_anchor":"plugin-hooksjson-accepts-a-schema-key","heading":"Plugin hooks.json accepts a $schema key","tier":null,"area":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/plugin-hooksjson-accepts-a-schema-key","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Plugin hooks.json accepts a $schema key\n\nA plugin's hooks.json file can now include a `$schema` key, which Claude Code ignores when loading\n\n**What**\n\nA plugin's `hooks.json` file may now contain an optional `$schema` entry. Its value is a link to a JSON Schema, a description of the file's allowed layout that a code editor can read. Claude Code ignores this entry when it loads the file. Other plugin files already accepted it.\n\n**Why**\n\nPlugin authors can point their editor at a schema for `hooks.json`. The editor can then suggest fields and flag mistakes while they write the file. The entry has no effect on how the hooks run."}