{"version":"2.1.287","anchor":"sessionstart-hooks-can-run-for-newly-added-plugins-only","canonical_anchor":"sessionstart-hooks-can-run-for-newly-added-plugins-only","heading":"Groundwork for running SessionStart hooks of plugins added mid-session","tier":"soon","area":"Hooks","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287\/e\/sessionstart-hooks-can-run-for-newly-added-plugins-only","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287","markdown":"### Groundwork for running SessionStart hooks of plugins added mid-session\n\nClaude Code now tracks which plugins' SessionStart hooks have run and can pick out plugins loaded later whose hooks have not\n\n**Unclear.** It is not clear what triggers these hooks to run, or whether this is switched on.\n\n**What**\n\n`SessionStart` hooks are scripts that run when a session begins or resumes, and plugins can supply them. Claude Code now keeps track of how the session started, which plugins its `SessionStart` hooks already covered, and whether they have been run. From that it can work out which plugins loaded later, for example after a reload, have `SessionStart` hooks that have not run yet.\n\n**Why**\n\nThis points to `SessionStart` hooks firing for plugins you add during a session, not only for plugins present at startup.\n\n- Area: Hooks\n- Tier: Nothing to try yet\n- Useful: 3\/5\n- Signal: 4\/5\n- Present in the build but not switched on"}