Repository navigation
Add Discord, Teams, iMessage, and WhatsApp channel adapters - #17
Merged
Merged
Conversation
moe-berri
marked this pull request as ready for review
October 12, 2026 18:58
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.
AgentChat can now receive messages and send confirmed text replies through Discord, Microsoft Teams, iMessage via BlueBubbles, and WhatsApp Business Cloud API. Each provider has its own package, optional dependencies, setup guide, and framework-free echo example.
The adapters preserve provider/account/conversation identity and attachment references, bound pending handlers, drain or cancel work on shutdown, and reject missing send receipts. The shared private dispatch helper contains no provider imports. Provider imports stay inside their own packages, following the containment rules on current main.
This first pass implements the minimum Channel contract. Native history, rich replies, file transfer, mirroring, and working indicators use the existing unsupported-capability behavior on these new adapters. Setup guides document conversation routing, text limits, delivery limitations, and live verification steps.
Validation:
ruff check .passed.python -m pytest: 342 passed on Python 3.12.14, including real local HTTP/Socket.IO round trips, Microsoft/Discord SDK parsing/routing, authentication rejection, receipt failures, queue limits, cancellation, and import isolation.No live provider credentials or destinations were used. This is a draft pending the documented live echo checks against provisioned accounts.
The branch contains six focused implementation/test commits and a merge adapting them to upstream main through b85fb2d (including the Slack transport-composition and reply-routing changes).