Add proactive threading support#523
Merged
Merged
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
Note
Copilot was unable to run its full agentic suite in this review.
Adds proactive threading support to the Apps SDK by introducing a stable way to construct threaded conversation IDs and a new proactive app.reply() API that can target channel threads.
Changes:
- Added
toThreadId()+supportsThreading()utilities for threaded conversation ID handling. - Added overloaded
App.reply()for proactive thread sends (threaded in supported scopes, flat otherwise). - Added a new
examples/threadingsample and clarifiedcontext.send()/context.reply()doc comments.
Reviewed changes
Copilot reviewed 11 out of 12 changed files in this pull request and generated 5 comments.
Show a summary per file
| File | Description |
|---|---|
| packages/apps/src/utils/thread.ts | Introduces thread ID construction + threading support detection. |
| packages/apps/src/utils/thread.spec.ts | Adds unit tests for toThreadId(). |
| packages/apps/src/utils/index.ts | Re-exports toThreadId() from utils barrel. |
| packages/apps/src/index.ts | Exposes toThreadId() on the package public API. |
| packages/apps/src/contexts/activity.ts | Updates doc comments to clarify send vs reply behavior. |
| packages/apps/src/app.ts | Adds proactive reply() overloads and threading guard usage. |
| packages/apps/src/app.spec.ts | Adds tests for new App.reply() behavior. |
| examples/threading/* | Adds a runnable example demonstrating threading usage. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
corinagum
force-pushed
the
cg/threaded-replies
branch
from
April 14, 2026 23:29
fdfe803 to
69cb411
Compare
heyitsaamir
reviewed
Apr 15, 2026
heyitsaamir
previously approved these changes
Apr 17, 2026
Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]>
corinagum
force-pushed
the
cg/threaded-replies
branch
from
April 17, 2026 16:34
635400d to
d462e2b
Compare
heyitsaamir
approved these changes
Apr 17, 2026
heyitsaamir
left a comment
Collaborator
There was a problem hiding this comment.
Threads is coming to DMs too, so supportsThreads will likely evolve soon!
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.
Summary
app.reply(conversationId, messageId, activity)for proactive thread sends — constructs threaded conversation ID viatoThreadedConversationId()for channels and 1:1 chats that support threadingtoThreadedConversationId()helper exposed for advanced scenariossupportsThreading()internal guard (channels:@thread.tacv2/@thread.skype, 1:1:@unq.gbl.spaces)context.send()andcontext.reply()doc comments to clarify threading vs quoting behaviortest reply,test send,test proactive,test manualTest plan
toThreadedConversationId()(9 tests),supportsThreading()(5 tests), andapp.reply()(6 tests)🤖 Generated with Claude Code