CoPilot Studio - SendActivityAsync stream ends, but things are still in progress

[graemefoster]

Language/Version
What package version of the SDK are you using.

• Language: C#
• Package version: 1.4.1-beta
• SDK Use: Agents Hosting / Clients / Tools. dotnet 10, using CoPilot Studio Agent

Describe the bug

I have a CoPilot Studio Agent that talks onwards to a Microsoft Foundry Agent.
When I watch the eventstream, it stops when Copilot Studio sends a message to the Foundry Agent.

I see the same in the CoPilot Studio portal, however the web-interface then makes a further /subscribe call, where I see more events followed by the eventual message.

My problem is, the SDK gives me no way to 'subscribe' when the initial message stream stops.

To Reproduce
How can we reproduce this error?

Create a CPS Agent, hook it up to a Foundry one, auto-approve the call in CPS. In the portal you'll see this:

But the Client SDK won't do this. You'll end on an event message, and get nothing else from the stream.

[sarahcritchley]

Hi @graemefoster - The current experience you describe is correct where if you are using the Copilot Studio Agent and using the preview functionality for connecting an Azure Foundry Agent - this currently supports single turn conversations only, and not multi-turn.

In this repo we do not manage Copilot Studio Features/Feedback but I have sent your feedback to the team working on this feature. There are plans to expand this support for multi-turn, no ETA yet.

[graemefoster]

@sarahcritchley got it - so when CoPilot Studio makes a jump to a remote agent like that, it's considered multi-turn from the CoPilot Studio's perspective even though it looks like a single turn to the user?

[sarahcritchley]

For Foundry specifically, when the agent is invoked, and the message is sent to foundry Agent, and returns a response, that is considered a single turn. The team are actively working on keeping that connection open, having the ability to send follow up messages, and ending the conversation.

[graemefoster]

So should I see a response that traverses all the way to the foundry agent, on a single turn from the end user? At the moment the response I get back is only half of that single turn on the CPS side.

[nurkmez2]

Any updates?