fix(msteams): correct typing indicator sendActivity call#1810
Merged
shakkernerd merged 3 commits intoopenclaw:mainfrom Jan 27, 2026
Merged
fix(msteams): correct typing indicator sendActivity call#1810shakkernerd merged 3 commits intoopenclaw:mainfrom
shakkernerd merged 3 commits intoopenclaw:mainfrom
Conversation
shakkernerd
reviewed
Jan 27, 2026
| const core = getMSTeamsRuntime(); | ||
| const sendTypingIndicator = async () => { | ||
| await params.context.sendActivities([{ type: "typing" }]); | ||
| await params.context.sendActivity([{ type: "typing" }]); |
Member
There was a problem hiding this comment.
sendActivity method only takes in an activity object and not an array of activity objects.
shakkernerd
added a commit
that referenced
this pull request
Jan 27, 2026
zooqueen
pushed a commit
to hanzoai/bot
that referenced
this pull request
Mar 6, 2026
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
3 participants
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.
Summary
Typing indicators in Microsoft Teams are now correctly sent as a single typing activity, ensuring the typing status is shown consistently to users.
Problem
Previously, the dispatcher used
sendActivitiesto send a typing indicator, which did not correctly surface the typing status in Microsoft Teams.As a result, users would not see a typing indicator even when the bot was actively composing a response.
Changes
Updated
createMSTeamsReplyDispatcherinreply-dispatcher.tsto usesendActivityinstead ofsendActivitieswhen sending a typing indicator.This aligns the typing behavior with the expected Bot Framework API usage for single typing events in Microsoft Teams and fixes an issue where the typing indicator was not displayed.
Test Plan
Verified that sending a reply which triggers a typing event now results in a visible typing indicator in a Microsoft Teams conversation.