Copilot Cowork: treat the OneDrive session folder as your system of record
luisdans · x · 2026-11-03
buckleyplanet breaks down Copilot Cowork's runtime data flow with an infographic: there are two stores — a per-session OneDrive folder users can see, and a short-lived isolate that vanishes when the task ends. Practical advice: treat the session folder as the system of record, have Cowork write cleaned workbooks to Output, and never assume a join survives the task. Key facts: the isolate is Microsoft-managed inside the M365 boundary; orchestration (plan + approvals) is durable; history goes to Purview; in-sandbox work is deleted with the task — handoff via files, not state.
More from coding & agent
- Obsidian dev open-sources Pele, a Mermaid-compatible renderer 100-500x faster than mermaid.js — Teknium · 2026-11-03
- Agent-built eval harness spawns subagents via codemode in one durable session — mitsuhiko · 2026-11-03
- Impeccable crosses 100k GitHub stars, with weeks of releases teased ahead — jamdac · 2026-11-03
- Every to demo 'Compound Sandwich': which engineering workflows to hand to agents — every · 2026-11-03
- Every launches an AI coworker in Slack that turns tagged tasks into reusable team skills — every · 2026-11-03
- Founder runs 2 AI companies with 8 Grok bots: Chief, PA, email, ads and GTM agents — alexgoughcooper · 2026-11-03