Add Session_ID to Hook Inputs

[ala24013]

Describe the feature or problem you'd like to solve

Hook input jsons lack a session_id field

Proposed solution

Currently the copilot cli session id is not passed in to hooks when they execute. This should be added as a common field across the hook Input Jsons. This would allow any code executing as a result of the hook to have an authoritative answer for its origin.

Example prompts or workflows

Any cases where hooks are used across multiple copilot cli instances concurrently.

As an example, the service I am working on facilitates cooperative AI cli interactions (primarily hook driven) and needs to be able to disambiguate between which of the local cli sessions invoked the hook.

Additional context

Copilot CLI Hook Inputs: https://docs.github.com/en/copilot/reference/hooks-configuration
Claude Equivalent: https://code.claude.com/docs/en/hooks#hook-input-and-output

[mjrousos]

Hi @ala24013, I took a look at this, and it looks like Session_ID is already included in hook inputs!

I'm using Copilot CLI version 1.0.11-0 and see the following as inputs to sessionStart and userPromptSubmitted hooks (notice the sessionId parameter):

=== Hook: session-start ===
Input:
{
  "sessionId": "714bfd7c-a8ef-4bde-8bea-ec39ceec45e8",
  "timestamp": 1774281852263,
  "cwd": "C:\\scratch\\HooksExploration",
  "source": "new",
  "initialPrompt": "Hello"
}
=== Hook: user-prompt-submitted ===
Input:
{
  "sessionId": "714bfd7c-a8ef-4bde-8bea-ec39ceec45e8",
  "timestamp": 1774281850955,
  "cwd": "C:\\scratch\\HooksExploration",
  "prompt": "Hello"
}

I think this is just a docs issue. I believe sessionId is always passed as a hooks input (along with timestamp and cwd) and our docs just need updated to mention that.

[ala24013]

@mjrousos Confirmed! Apologies for the churn on this. It does appear this is simply a documentation issue. Thank you!