Python sample Playground debugging uses Windows-only paths and PowerShell command on macOS

Description:

Summary

The README includes macOS environment setup, but the sample’s VS Code F5 configuration contains Windows-specific interpreter paths, a Windows PATH separator, and a PowerShell executable name unavailable on Mac.

Sample: https://github.com/microsoft/Agent365-Samples/tree/main/python/agent-framework/sample-agent

Environment

macOS on Apple Silicon, Python 3.11.15, PowerShell 7.6.0 installed as pwsh.

Steps to Reproduce

Create the documented virtual environment on macOS, install PowerShell, and select Debug in Microsoft 365 Agents Playground in VS Code. The configuration references these incompatible values:

Expected Behavior

The documented Playground debug workflow should resolve the correct interpreter and executables on macOS without manual configuration changes.

Suggested Resolution

Use portable interpreter discovery and platform-specific overrides for the Python launch, Playground PATH, and token-refresh task. I applied macOS overrides locally while retaining the Windows defaults; VS Code configuration checks pass.

In the sample-agent VS Code configuration, inspect settings.json, launch.json, and tasks.json first. Compare the Python interpreter, Playground PATH, and token-refresh command settings with the documented macOS workflow, then run the VS Code configuration checks. Done means the Playground debug workflow works on macOS while retaining the Windows defaults.