{"version":"2.1.318","anchor":"mods-classicsessionstart-hook-refuses-calls-in-pre-started","canonical_anchor":"mods-classicsessionstart-hook-refuses-calls-in-pre-started","heading":"Some mod calls are refused in a classic.SessionStart hook on pre-started sessions","tier":"notice","area":"Mods","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318\/e\/mods-classicsessionstart-hook-refuses-calls-in-pre-started","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318","markdown":"### Some mod calls are refused in a `classic.SessionStart` hook on pre-started sessions\n\nIf a host started the session early, some mod calls made from a `classic.SessionStart` hook are now refused instead of hanging\n\n**Unclear.** It is not clear which mod calls this applies to.\n\n**What**\n\nA mod is a user-written add-on, and a hook is code a mod runs when something happens. Some sessions are started ahead of time by the host, the program running Claude Code. In those sessions, certain calls made from a `classic.SessionStart` hook are now refused. The message says to run the code from `session.start` or a later event such as `turn.complete`.\n\n**Why**\n\nThese calls would wait for start-up to finish, but start-up is itself waiting for the hook, so the session would hang. Mod authors whose code is refused should move it to one of the later events.\n\n- Area: Mods\n- Names: `classic.SessionStart`, `session.start`, `turn.complete`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: yes"}