{"version":"2.1.300","anchor":"hooks-carry-settingssource","canonical_anchor":"hooks-carry-settingssource","heading":"Hooks now record which settings they came from","tier":"internal","area":"Hooks","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300\/e\/hooks-carry-settingssource","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300","markdown":"### Hooks now record which settings they came from\n\nEach hook's record can now include the settings source it was defined in\n\n**What**\n\nA hook is a command you configure to run automatically at certain points in a session. Hooks can be defined in more than one settings file. Claude Code's record of each hook now includes a `settingsSource` field, naming where the hook was set up, whenever that is known.\n\n**Why**\n\nA hook can be traced back to the settings it came from.\n\n- Area: Hooks\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}