Cowork steps off the desktop

Monday AI Dispatch -05

It happened to me last week. I was between meetings in the office, standing in a hallway with a coffee in one hand and my phone in the other, and I remembered the follow-up I owed a client before end of day. The old reflex was to make a mental note, hope I remembered when I got back to the laptop, and then spend ten minutes context-switching to write the thing. Instead, I opened Copilot on my phone, told Cowork what I needed, and kept walking to my next meeting.

On May 5, Microsoft announced that Copilot Cowork is now available on iOS and Android as part of the latest Frontier wave. That’s a quietly important shift, and it’s worth a few minutes of your attention.

What Actually Changed

If you’ve been reading along, you already know the story. Cowork moves Copilot from “give me an answer” to “go do the work.” You describe an outcome. Cowork builds a plan. It coordinates across Outlook, Teams, Word, Excel, and SharePoint, runs in the background, and checks back in at the moments where it actually needs you.

Cowork already ran in the cloud, so your laptop didn’t need to be open for work to keep moving. Now the entry point follows you. The Microsoft 365 Copilot mobile app on iOS and Android gives you the same Cowork experience you’ve been using in the browser and on desktop. You can kick off a task on the train, approve an action between meetings, and come back to a finished outcome.

See it in action

A few things worth pointing out in the video:

• The approval prompts look and behave the same as on desktop. Medium and high-risk actions still get a risk indicator before anything is sent.
• Tasks queue up. If I send a second message while Cowork is still working, it doesn’t interrupt the first one it picks it up in order.
• Cowork keeps running after I lock the phone. Because the work happens in the cloud, I’m not babysitting a process on the device.

Where Mobile earns its keep

The desktop scenarios I wrote about a couple of weeks ago, digging out of a post-conference inbox, untangling a calendar. Those still belong on a real keyboard.

Mobile Cowork is for the in-between moments. Here is how I have been using it.

The “before I forget” delegation.

“Draft a follow-up email to [Client Name] thanking them for today’s meeting, summarize the three action items I committed to, and propose two times next week for a working session. Save it to drafts, do not send.”

I send that from my phone, Cowork builds the draft against my actual calendar availability, and it sits in my Outlook drafts when I get back to the laptop. Five seconds of typing on mobile saves me twenty minutes of context-switching later.

The pre-meeting prep on the walk in.

“I have a 1:1 with [Name] in 15 minutes. Pull our last three Teams threads, any shared documents updated in the past two weeks, and give me three discussion points based on what is open between us.”

This is the Daily Briefing and Enterprise Search skills doing what they already do — just sized to a thumb scroll instead of a monitor.

The approval-in-flight.

This is the one that surprised me. I had a long-running Cowork task going from earlier in the day. While I was out, it hit a decision point and queued an approval. The mobile app surfaced it as a notification, I tapped through, reviewed the recommended action, and approved it from the parking lot. The plan kept moving without me losing an evening to catch-up work.

Build Yourself a Pocket Skill

Here is where mobile gets really interesting. Cowork supports custom skills reusable workflows that turn a short, half-typed prompt into a fully-formed task. Skills are exactly the kind of leverage you want when your input device is two thumbs.

A skill is a folder in your OneDrive at /Documents/Cowork/skills/[skill-name]/ containing a single SKILL.md file. The file has YAML frontmatter at the top and a Markdown workflow underneath. That is the whole format. The same Agent Skills standard is used by Claude Code, VS Code Copilot, Cursor, and a dozen other tools, so it is portable.

Here is a working example I built for myself a meeting follow-up skill that lives at /Documents/Cowork/skills/meeting-follow-up/SKILL.md

---
name: meeting-follow-up
description: |
  Drafts a follow-up email after a meeting with action items and proposed
  next-meeting times. Use when user asks to "send a follow-up", "draft a
  thank-you after my meeting", "follow up with [name]", or "send action
  items from this morning's call".
license: MIT
metadata:
  author: Pat Petersen
  version: "1.0"
cowork.category: Productivity
---
# Meeting Follow-Up
## What This Skill Does
Generates a follow-up email after a meeting that:
- Thanks the attendees and recaps the conversation in two or three sentences
- Lists the action items with owners and rough due dates
- Proposes two times for the next working session based on my actual availability
- Saves to drafts in Outlook — never sends without explicit approval
## Workflow
1. Identify the meeting. If the user names one, use that. Otherwise use the
   most recent past meeting from my calendar within the last 24 hours.
2. Pull context from the meeting: attendees, the meeting description, any
   linked or attached files, and the Teams chat thread if one exists.
3. Generate the draft using the format below.
4. Check my Outlook calendar for the next 10 business days and propose two
   30-minute slots that work for the primary attendee.
5. Save to Outlook drafts. Do not send. Present the draft to me for review.
## Output Format
**Subject:** Following up: [Meeting Title]
**Body:**
- Opening line: one-sentence thanks tied to a specific thing discussed
- Recap: two to three sentences on what we aligned on
- Action items: a short bulleted list, each item formatted as
  `[Owner] — [Action] — [By when]`
- Next step: "I have time [Option A] or [Option B] for a 30-minute working
  session. Either work?"
- Sign-off: "Thanks, Pat"
## Tone
Direct, warm, and short. No filler phrases like "I hope this email finds
you well." No marketing language. If the meeting was internal, drop the
formality further.

Ask Cowork to save that file in the right OneDrive path. On your next Cowork session, the skill loads automatically and triggers when you use one of the phrases in the description.

• Now, from my phone, I can type:
  • “Follow up on this morning’s call with [Name].”
    • Nine words. Cowork pulls the meeting context, applies the structure I defined, checks my calendar for next-session times, and parks a draft in Outlook. When I get back to the laptop, I review and send. Without the skill, that same outcome takes a 60-word prompt and produces an email that may or may not match the structure I want.
• A few notes from building this:
  • The folder name must match the name field exactly, in kebab-case. Microsoft Learn flags this as the single most common cause of skills failing to load.
  • Description quality is what triggers the skill. Be specific about the phrases you actually say. “Follow up on my meeting” is the kind of casual phrasing that should match.
  • Keep the SKILL.md body lean. If you find yourself writing more than a couple thousand words, move the deep content into a references/ subfolder.
  • The same SKILL.md works in Claude Code if you copy it into .claude/skills/. If you author there first and want to ship to a wider audience inside your org, Microsoft provides a PowerShell conversion script that packages it as a sideload-able M365 plugin.
  • Once you have one skill working, you will start seeing skill-shaped problems everywhere. Pre-meeting prep, end-of-day wrap, weekly status update, RFP response intake.

What to Expect (and What Not To)

A few honest notes, because Cowork is still in Frontier preview and mobile is new.

• The prompt quality discipline still applies. Vague delegation produces vague plans, and that gets worse on a small screen where typing is more effort. I save common prompt patterns in a note on my phone and paste them in.
• Do not skip the approval steps. Especially on mobile, where it is tempting to thumb-tap through prompts, slow down on anything that sends email, posts in Teams, or modifies a calendar. The whole point of Cowork’s checkpoint design is that you are still the one accountable for what goes out.
• Network matters. Cowork runs in the cloud, but the conversation surface is on your phone.
• Finally and this is the part I keep telling clients; mobile Cowork is not a replacement for sitting down and thinking. It is a way to close the gap between thinking about the work and the work being in motion.

Related Content

• Copilot Cowork: From conversation to action across skills, integrations, and devices — Microsoft 365 Blog, May 5, 2026
• Copilot Cowork overview — Microsoft LearnBuild plugins for Copilot Cowork — Microsoft Learn
• Get started with Copilot Cowork — Microsoft Learn
• Let Copilot Cowork Dig You Out — Monday AI Dispatch 03
• Copilot Cowork: Microsoft’s Bold Leap from AI Assistant to AI Executor

The post Cowork steps off the desktop appeared first on Pat Petersen.

Original Post https://patpetersen.com/2026/05/11/cowork-steps-off-the-desktop/