White paper: Choosing between the GitHub Copilot and Standard harnesses in Copilot Studio

This is a fantastic whitepaper. I plan to use it when guiding clients on which harness to use. It makes a strong case for the Standard Harness for the proper scenarios.

At the same time, the "New experience" UI in Copilot Studio completely throws the Standard Harness under the bus. Right now, Copilot Studio implementers must reconcile the guidance from your whitepaper with the highly strong visual cues insinuating the Standard Harness's days are numbered.

I'm not here to complain but rather offer a solution. Copilot Studio "New Experience" and traditional Copilot Studio are completely different products serving two different needs. Here is what I propose:

• Copilot Studio "New Experience" is rebranded to Copilot Cowork Studio. This makes all the sense in the world. Agents created in "New Experience" drive complex business processes in ways equivalent to the end-user Copilot Cowork. They aren't copilots, they are coworkers. Copilot Cowork Studio is the maker's answer to Copilot Cowork.
  
  
• Copilot Studio continues its existence as a Copilot creator, geared toward interactive sessions with users. By untangling "New Experience" from Copilot Studio, there is once again a clean roadmap for improving what is a fantastic product.
   

The potential of these two amazing products can truly be unlocked if they are recognized as two separate amazing products. I encourage Microsoft to do so.