Add proactive messaging support to AgentApplication #771
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
packages/agents-hosting/src/app/proactive/…) that captures the pair(TurnContext.identity, ConversationReference)on every turn,supports manual get/save/delete, honors optional TTLs, and uses storage eTags for optimistic concurrency
AgentApplication.proactive, wired through newproactiveOptions, so apps can auto-persist references, retrieve them later, and callsendActivities/sendToReferenceto deliver proactive activity batches while getting back the connector’s activity IDsregisterProactiveRoutes) that surfaces/api/sendactivityand/api/sendtoreference, enabling external services (e.g., backgroundjobs, contact centers) to trigger proactive sends without hand-rolling Bot Framework plumbing
proactive send, TTL expiry, missing-reference error path)
Resolves #336, #414 & #159