{"version":"2.1.286","anchor":"new-inputsource-field-and-tool-name-passed-on-hook-progress","canonical_anchor":"new-inputsource-field-and-tool-name-passed-on-hook-progress","heading":"Messages now record where input came from, and hook progress names the tool","tier":"internal","area":"Hooks","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286\/e\/new-inputsource-field-and-tool-name-passed-on-hook-progress","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286","markdown":"### Messages now record where input came from, and hook progress names the tool\n\nYour turns now carry a note of where the input came from, and hook progress entries now include the tool's name\n\n**Unclear.** What reads these new fields, and whether either shows up anywhere a user can see.\n\n**What**\n\nTwo pieces of information are now recorded:\n\n- Your turns in the conversation now carry a note of where the input came from, when that is known.\n\n- Hook progress entries now include the name of the tool involved. Hooks are commands Claude Code runs automatically at set moments.\n\n**Why**\n\nThese are records for other parts of Claude Code to read. Nothing here changes what you do.\n\n- Area: Hooks\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}