Microsoft AI
Member of Technical StaffConsumer Copilot and Copilot Tasks
I work on Consumer Copilot model behavior and architected the Copilot Tasks response layer. The walkthrough starts with image results and the chat handoff, then follows presentation, shopping, document, and app requests to explain planning, tools, inference caching, and evaluation.
Copilot Tasks reached 200k daily active users in under a month. Separately, I approved model-feature evaluations and led an evaluation harness profiling 1,000+ coding-agent PRs per week.
Image results and guided follow-ups
Copilot answers a presentation-style question with image references and a suggested follow-up. I co-owned the main system prompt and worked on these model features as one of five feature owners, serving 100M monthly active users.
Starting a task from chat
That presentation request moves from chat into Tasks. I built this handoff: Start launches the work, and Open reveals its plan. The chat-to-Tasks path accounted for about 70% of Tasks usage.
Loading skills and source access
The plan loads a presentation skill, reads Drive notes, and checks web sources. I implemented skill loading and explored selecting connector permissions before consent, including read access without email-send permission.
Producing the slide deck
I architected the response layer coordinating plans, tools, and artifacts. Here, the gathered inputs produce the requested slide deck; that same deck carries into the preview.
Keeping the task context
A new shopping request specifies size M and a $60 budget. Those constraints stay in the task brief while tool results are added. My inference caching and context-management work reduced Copilot spend by $2M+ per month.
Batching browser operations
For that shopping task, predictable browser actions run in one batch instead of separate model round trips. I worked on this browser-use guidance; the grouped Open, Read, and Compare actions show the batch.
Recovering from repeated work
The browser returns the same page again. I worked on instructions for recognizing repeated work and changing approach; the task now replans around another source instead of repeating the request.
Reviewing the selected item
The shopping task has selected an item that fits the requested size and budget. It reaches a review step and waits for purchase approval.
Checking the task result
The selected item is checked against the $60 budget and size M. The final check confirms that checkout is still waiting for approval.
Turning notes into a brief and draft
A separate document request uses the same launch notes to produce a brief and email draft. The three sheets belong to that one task: source note, derived document, then draft awaiting approval.
Generating a runnable app
A separate request produces an app instead of a document. Its artifact becomes the paper-plane game, with keyboard and touch input, scoring, pause, and restart controls.
The illustration loads as you approach. The story is ready to read.