{"version":"2.1.273","anchor":"sessionstart-hook-execution-now-receives-an-agentcontext-par","canonical_anchor":"sessionstart-hook-execution-now-receives-an-agentcontext-par","heading":"SessionStart hook execution now receives an agentContext parameter","tier":"internal","area":"Hooks","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273\/e\/sessionstart-hook-execution-now-receives-an-agentcontext-par","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273","markdown":"### SessionStart hook execution now receives an agentContext parameter\n\nSessionStart hooks now receive an extra agentContext parameter when they run\n\n**Unclear.** What information agentContext carries or what new capability it gives to SessionStart hooks is not stated.\n\n**What**\n\nA hook is a script you configure to run automatically at certain points in a session. The internal function that runs `SessionStart` hooks (which fire when a session begins or resumes) and loads plugin hooks now also accepts and passes along a new `agentContext` parameter, alongside existing options like credentials, the cancellation signal, and whether the session is orphaned.\n\n**Why**\n\nThis gives the hook-running machinery more context about the agent it's running for, though the finding doesn't specify what new behavior this enables for hook authors.\n\n- Area: Hooks\n- Names: `SessionStart`\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}