feat: add agent_session_stopped and agent_session_title_changed events - #1635
Draft
zimeg wants to merge 1 commit into
Draft
feat: add agent_session_stopped and agent_session_title_changed events#1635zimeg wants to merge 1 commit into
zimeg wants to merge 1 commit into
Conversation
Adds event models, payload wrappers, and handler base classes for the two agent session events an agent app receives, mirroring the assistant event pattern. Payload fields captured from live events. - agent_session_stopped: type, channel, user, thread_ts, streaming_message_ts (array), event_ts - agent_session_title_changed: type, channel, user, team_id, thread_ts, title, previous_title, event_ts Co-Authored-By: Claude <svc-devxp-claude@slack-corp.com>
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #1635 +/- ##
============================================
- Coverage 72.87% 72.85% -0.03%
Complexity 4522 4522
============================================
Files 479 481 +2
Lines 14390 14394 +4
Branches 1503 1503
============================================
Hits 10487 10487
- Misses 3013 3017 +4
Partials 890 890
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds Events API support for the two agent session events an agent app receives, mirroring the existing assistant event pattern (event model + payload wrapper + handler base class per event).
Events
type,channel,user,thread_ts,streaming_message_ts(list),event_tstype,channel,user,team_id,thread_ts,title,previous_title,event_tsWhat's included
AgentSessionStoppedEvent,AgentSessionTitleChangedEvent(slack-api-model)AgentSessionStoppedPayload,AgentSessionTitleChangedPayload(slack-app-backend)AgentSessionStoppedHandler,AgentSessionTitleChangedHandlerNo central registry to edit — event routing is by reflection over the event
type, soapp.event(AgentSessionStoppedEvent.class, handler)self-registers (consistent with the other event types).Notes
agent_session_title_changedcarriesteam_idon the inner event;agent_session_stoppeddoes not (it carriesstreaming_message_ts, the timestamps of any in-flight streaming messages at stop time). Envelope-level fields (enterprise_id,team_idon the wrapper,authorizations) live on the payload wrapper, not the inner event.Category
Requirements
Please read the Contributing guidelines and Code of Conduct before creating this issue or pull request. By submitting, you agree to those rules.