Microsoft moves Copilot's hand-off features onto usage billing in a rebuilt desktop app

Microsoft's own example for the new Copilot app is a supplier review. "It can do things like set up and manage a full supplier review process: building the schedule and workback plan, then handling prep, meetings, and follow-ups on its own, right down to reaching out to stakeholders for updates," Jared Spataro, Microsoft's Chief Marketing Officer of AI at Work, wrote ^[6]. The person who asked for it can log off. "Autopilot is cloud-hosted, so it keeps working while you sleep or your attention is elsewhere," Spataro said ^[7].

Spataro pitched the release in large terms. "Just as Office defined productivity for the PC era, Copilot is defining work for the AI era," he said ^[17]. The thing being shipped is a desktop app with tabs and a price list. Under that price list, three of the four modes a user can reach are metered ^[16]. Thurrott reports the pricing change is meant to help organizations manage their AI spend ^[12].

A pilot report that counts seats and weekly chat users is describing the licensed half of the product, the half that costs the same whether anyone delegates anything ^[3]. The meter will show how often staff handed work over. It will not show whether the work came back finished or had to be redone.

Choosing a mode is also about to get harder to see. Spataro said that soon "you won't need to choose a mode" ^[14], with Copilot sending each request to Chat, Cowork, Code or whichever capability suits it ^[15]. With this billing split, the router also decides whether a request lands on the seat license or the meter. Microsoft has not said whether users will be told when a request moves to a metered mode.

Engadget set the release against Microsoft possibly "taking a step back from shoving AI and Copilot features into Windows" ^[19]. For IT, the governance work moves into one app that holds chat, coding and the agent ^[1]. Its Code tab syncs with the standalone GitHub Copilot service ^[2], and How-To Geek reports it is sandboxed so it should not run loose on the network ^[4].

The recommendation for a Frontier pilot is to sort tasks before switching on the metered tabs. Use two tests: whether the task recurs, and whether its owner can check the result without redoing it. Recurring, easy-to-check work, such as chasing weekly status updates, is the best case for paying Autopilot's meter. If the work recurs but is hard to check, it bills every cycle and needs a reviewer every cycle, so it belongs in Cowork with a human sign-off. Easy one-offs can stay in Chat, which the seat license already covers. Hard one-offs cost the most to delegate and save the least. The tradeoff is that a pilot started in the first box will undercount what the agent can do on a project the size of Spataro's supplier review. It will also give finance a number it can check: tasks finished per unit of metered spend.