{"version":"2.1.280","anchor":"hook-execution-context-now-exposes-hookorigin-and-hookcaller","canonical_anchor":"hook-execution-context-now-exposes-hookorigin-and-hookcaller","heading":"Hook execution context now exposes hookOrigin and hookCaller","tier":"internal","area":"Hooks","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/hook-execution-context-now-exposes-hookorigin-and-hookcaller","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### Hook execution context now exposes hookOrigin and hookCaller\n\nHooks can now read a new hookOrigin and hookCaller from their execution context\n\n**Unclear.** The finding does not say what values these getters actually return or how hook authors are meant to use them.\n\n**What**\n\nThe object that hooks (scripts Claude Code runs automatically at certain points) can query for context now exposes two new pieces of information: `hookOrigin` and `hookCaller`, alongside the existing `agentContext` and `agentWorktree` values.\n\n**Why**\n\nThis gives hook authors more information about where and by what a hook was triggered, which can help a hook behave differently depending on its origin or caller.\n\n- Area: Hooks\n- Names: `hookOrigin`, `hookCaller`\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}