Multi-agent workspaces: no way to choose which hosted agent Inspect Locally and Test in Foundry Portal use

[qinezh]

Description

A workspace can legitimately contain more than one Foundry hosted agent — for example a repo with several azure.yaml files that each declare a host: azure.ai.agent service. The Deploy & test section of the Microsoft Foundry canvas gives no indication of which of those agents its actions apply to, and offers no way to change it.

• Inspect Locally always runs the first agent returned by the workspace scan. The scan walks the workspace breadth-first with directory entries sorted alphabetically, so the agent that gets run is effectively decided by folder naming rather than by the user.
• Test in Foundry Portal does not appear at all. When the scan finds more than one hosted agent the resolution returns an ambiguous_agent result, and the canvas suppresses the portal link instead of asking which agent to open. The user loses the action entirely.

Steps to reproduce

1. Open the Microsoft Foundry canvas in GitHub Copilot App.
2. Open a workspace that declares two or more hosted agents — e.g. two folders, each with an azure.yaml containing a host: azure.ai.agent service.
3. Expand the Deploy & test section.
4. Click Inspect Locally.

Current behavior

• Nothing in the Deploy & test section names the hosted agent that its actions target.
• Inspect Locally starts whichever agent happens to sort first in the workspace scan. There is no way to inspect any of the other agents in the workspace.
• Test in Foundry Portal is hidden, so there is no way to reach the portal playground for any of the agents.

Expected behavior

• The user should be able to see which hosted agent Inspect Locally and Test in Foundry Portal apply to, and switch to a different one when the workspace has several.
• Test in Foundry Portal should stay available when a workspace has multiple hosted agents rather than disappearing.
• Workspaces with no hosted agent, or with exactly one, should behave exactly as they do today — there is nothing to disambiguate, so no extra UI should show up.

[microsoft-github-policy-service]

Thank you for contacting us! Any issue or feedback from you is quite important to us. We will do our best to fully respond to your issue as soon as possible. Sometimes additional investigations may be needed, we will usually get back to you within 2 days by adding comments to this issue. Please stay tuned.