Describe the bug
After the most recent update to Copilot CLI (1.0.25), the onSessionEnd hooks have introduced a regression.
Previously, the onSessionEnd hooks would be fired any time the copilot agent had sent a response message back to the user's input request and would be marked as a "completed". However, after the update, these copilot hooks are no longer firing whenever the copilot agent sends a response.
Now, the onSessionEnd is only firing when the user terminates their session entirely instead of also firing whenever the agent sent a response.
Affected version
1.0.25
Steps to reproduce the behavior
- Type a fake input command like "Hello"
- See a session start hook
- Wait for a response
- No session end hook is fired
The session end hook used to trigger in the previous version ^
Expected behavior
The session end hook should fire. If this was not intended, then a new hook should be created once the assistant sends it's final reply
Additional context
No response
Describe the bug
After the most recent update to Copilot CLI (
1.0.25), theonSessionEndhooks have introduced a regression.Previously, the
onSessionEndhooks would be fired any time the copilot agent had sent a response message back to the user's input request and would be marked as a "completed". However, after the update, these copilot hooks are no longer firing whenever the copilot agent sends a response.Now, the
onSessionEndis only firing when the user terminates their session entirely instead of also firing whenever the agent sent a response.Affected version
1.0.25
Steps to reproduce the behavior
The session end hook used to trigger in the previous version ^
Expected behavior
The session end hook should fire. If this was not intended, then a new hook should be created once the assistant sends it's final reply
Additional context
No response