{"version":"2.1.312","anchor":"config-tool-schema-runtime-values-description-and-plugin-ho","canonical_anchor":"config-tool-schema-runtime-values-description-and-plugin-ho","heading":"Hook schema gains a required sources field, and Config tool wording changes","tier":"notice","area":"Elsewhere","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.312\/e\/config-tool-schema-runtime-values-description-and-plugin-ho","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.312","markdown":"### Hook schema gains a required `sources` field, and Config tool wording changes\n\nA schema that carries a `shell` value now also requires `sources`, and the Config tool says its live values reflect what the next message will use\n\n**What**\n\nA schema is the definition Claude Code uses to check the shape of a piece of data. Two schema changes appear together.\n\n- `sources` field: the schema that adds an optional `shell` value to a base definition now also adds `sources`. Unlike `shell`, `sources` is required. The member titles connect it to hooks, which are your own commands that run at set points, and to plugin hooks.\n\n- Config tool wording: the Config tool lets Claude read and change settings. Its description of settings worked out while running now says they 'reflect what the next message will use'. Before, it said they reflected what 'will actually be sent to the API'.\n\n**Why**\n\nThe Config tool description is text Claude itself reads, so it now describes these values as what the next message will use. The new required `sources` field means the data this schema covers must now say where it came from.\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}