{"version":"2.1.287","anchor":"sessionstart-hooks-from-late-loaded-plugins","canonical_anchor":"sessionstart-hooks-from-late-loaded-plugins","heading":"Plugins loaded mid-session can no longer inject a starting message from SessionStart hooks","tier":"notice","area":"Hooks","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287\/e\/sessionstart-hooks-from-late-loaded-plugins","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287","markdown":"### Plugins loaded mid-session can no longer inject a starting message from SessionStart hooks\n\nIn a new mode, a SessionStart hook from a plugin loaded after the session began has its initial user message ignored, with a warning\n\n**Unclear.** It is not clear what makes Claude Code run hooks in the newly-loaded-plugins mode.\n\n**What**\n\nA hook is a command you or a plugin configure to run automatically at a certain moment. `SessionStart` hooks run when a session begins or resumes, and they can supply an initial user message to start the conversation with.\n\nClaude Code can now run hooks in a mode that covers only newly loaded plugins. In that mode, if a plugin was loaded after the session had already started, its `SessionStart` hook's initial user message is ignored and Claude Code shows a warning instead. Before, that message was always accepted. Claude Code also now keeps track of which plugins each matched hook belongs to.\n\n**Why**\n\nThis affects plugins you install while a session is already running: their start-of-session hooks no longer slip a message into a conversation that is already under way.\n\n- Area: Hooks\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5"}