Make sure we preserve the right session id/resource for agent calls #275973
+39
−19
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.
Counterpart of #275972 that fixes the issue is a better way for November
The main part of this change is avoiding the call to
LocalChatSessionUri.forSessionin mainThreadChatAgent. This call can't be used for non-local chat sessions. Instead we want to pass around the session's resource so we don't have to try mapping between ids and resources