Repository navigation
Add Slack Web API transport for HTTP event hosts - #24
Merged
Merged
Conversation
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.
Applications with signed Slack HTTP events and a durable outbox can now use AgentChat’s Web API transport without creating a Socket Mode connection or supplying an app-level token.
SlackWebApiexposes single-attempt GET and POST calls, preserves provider receipts, and rejects method strings that could change the destination. OAuth, refresh, and retry policy stay with the host.Validation: the full
agentchat-slacktest suite passed, including a loopback test for bot authentication, history reads, message updates, and invalid method rejection.