{"version":"2.1.296","anchor":"hooks-module-tracks-environmentargs-per-module","canonical_anchor":"hooks-module-tracks-environmentargs-per-module","heading":"Hooks modules keep their startup arguments while loaded","tier":"internal","area":"Hooks","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296\/e\/hooks-module-tracks-environmentargs-per-module","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296","markdown":"### Hooks modules keep their startup arguments while loaded\n\nClaude Code now stores each hooks module's arguments while it is loaded and discards them when it unloads\n\n**What**\n\nHooks are your own commands or scripts that Claude Code runs at set points. When a hooks module loads, Claude Code now stores the arguments it was given, filed under that module. It deletes them when the module unloads.\n\n**Why**\n\nThis is internal groundwork that lets those details be looked up per module. It does not change anything you see.\n\n- Area: Hooks\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}