The Three Modes of Claude Cowork: A Clinician’s Field Guide to Dispatch, Scheduled Tasks, and Live Artifacts
When to dispatch a task. When to schedule one. When to leave a live artifact running. A practical map of agentic work for the busy operator-clinician — with use cases that respect the realities of the
The Setup
If you’re reading this, you’ve probably already crossed the threshold from “AI as a chat tool” to “AI as a colleague” (or at least AI as an incredibly smart but occasionally dishonest junior intern”. The next layer is learning when to delegate synchronously, when to delegate on a recurring schedule, and when to leave a panel open that quietly refreshes itself from your connectors.
Claude Cowork gives you three modes of operation for this. I find many people don’t fully understand these three features in Claude Cowork. The goal of this guide — and the short companion video — is to make the choice obvious in the moment: “this is a Dispatch,” “this is a Scheduled Task,” “this is a Live Artifact.”
I’ll lean on a few clinical examples — but most of these patterns translate across any operator role: research PI, life coach, consultant, operator, founder, faculty, fund manager. A note up front: most clinical workflows are not yet HIPAA-compliant in consumer Claude, so I’ve erred towards the use cases that don’t need an EHR but are still in my opinion tremendously useful.
At a Glance — The Three Modes Side-by-Side
Tip: if your gut says “I want this once, but it’s big,” that’s a Dispatch. “I want this every Friday at 6am” — Scheduled Task. “I want a page I can refresh whenever” — Live Artifact.
The Cowork compliance boundary — Don’t pipe PHI through consumer Cowork.
The workflows above are for the life around clinical practice — schedules, citations, CME, calendars, communications. Consumer Claude Cowork is not HIPAA-compliant, and there is no BAA unless you sign of for the enterprise healthcare product. The clinical-adjacent examples here all assume de-identified inputs, scheduling exports, or operational data. Never patient charts, never PHI.
As Anthropic’s enterprise + BAA posture matures, this will shift. Until then, treat Cowork like a high powered personal email account and chief of staff: high leverage for your own work, not a place to ingest patient data.
The compliant alternative — RevelAi Health, for the work inside the EHR boundary.
For the workflows that touch the patient — care journeys, ambient note review, after-hours triage, PRO/PROM collection, quality reporting, HCC/CDI — We at RevelAi Health have BAA-backed, EHR-integrated system built for this gap. The same agentic patterns live inside a compliant boundary, with FHIR-native packaging instead of consumer connectors.
If a use case in this article needs to read or write clinical data, it almost certainly belongs in a specialized tool rather than Cowork. A patient-facing layer (like Kimi Care Coach) handles the journey side; the clinician-facing tools handle the documentation side.
Mode 01 — Dispatch: The Night-Shift Colleague
Dispatch is what you reach for when you have a single, sizeable task that you want executed right now while you’re away from your desk. Your desktop stays awake, your files and connectors stay accessible, and Cowork works on a deliverable until it’s done. The fastest way to brief a Dispatch is from your phone.
The mental model: imagine a thoughtful chief resident who shows up the moment you sign off and works through the night. You dictate the instruction set on the way out the door, and you find a draft on your desk in the morning.
Use it when you’re about to scrub in, board a flight, fall asleep, or sit through a 90-minute meeting — and the task is too big for a chat turn but too one-off for a schedule.
Use cases — clinical and adjacent
Prepared talk first-draft (Academic). Before a flight or an OR block: “Draft a 12-slide talk on the proximal humerus algorithm for next week’s CME — pull from my Substack archive and the AAOS guidelines folder, in the Techy Surgeon style.” Wake up to a strawman you refine over coffee.
Recent literature compilation (Research). “Pull the last 90 days of high-impact orthopaedic trauma literature on geriatric femur fractures, summarize each, and rank the three I should actually read.” A reading list waiting on landing — keeps your evidence base current without the weekly tax.
CME planning + trip proposal (Personal). “Look at my forwarded conference invitations in my inbox and my CME credit gaps for 2026. Propose a three-trip plan that hits required credits, balances family travel, and respects my OR block schedule.” A printable proposal you sanity-check Sunday night.
PHI-clean inbox triage (Operator). Before a long OR block: “Triage non-clinical email — admin, faculty, academic correspondence. Draft replies for the easy ones. Don’t touch anything that looks like a patient or family thread.” A sorted dashboard for the lounge. *Again there is the caveat that many folks are on outlook and their enterprise won’t let claude co-work into their emails, so I do a lot of email forwarding of safe correspondence into my other inbox and let claude dispatch do it’s think this way.
Manuscript pre-review pass (Research). Before a long flight (or on one if you have your laptop with you): “Run a peer-review pass on this draft in my recent emails (or you can drag file into chat box) — methodological gaps, missing citations, structural feedback. Output a redlined .docx and a one-page rationale.” Emerge from surgery with your redlined edits ready.
Conference itinerary + agenda mapping (Personal). “I’m at AAOS next week — pull the program, find the four sessions that match my research interests, suggest who to meet at the publisher’s reception, and map a printable schedule.” Walk into the meeting already oriented.
How to dispatch (the way I use it)
Make sure your desktop is awake, plugged in, and signed into Cowork. Disable sleep on AC power — battery saver silently kills a Dispatch.
Open the Claude app on your phone. Tap the menu in the top-left corner to expose the sidebar.
In the sidebar, tap Dispatch. The phone-side view connects back to the desktop you left awake.
Dictate the brief — I use WisprFlow to rattle off goal, context, files or connectors to use, output format, and where to save. The richer the dictation, the better the morning.
Send it. Put the phone away. (Browser and desktop entry points work too — this is just the path that gives me the most leverage.)
When you return to your desktop, Dispatch sits in the sidebar. Each task is its own session with the deliverable ready.
Pro tip: keep the laptop on a power outlet with sleep disabled — not just on battery. Sleep mode and battery saver are the two most common reasons a Dispatch silently fails to run.
Mode 02 — Scheduled Tasks: The Standing Meeting That Never Cancels
Scheduled Tasks are recurring. You set a cadence, point Cowork at the inputs, and it produces the same deliverable on the same rhythm — forever, until you turn it off. This is the mode I get the most leverage from, by a wide margin.
The trick is to identify the chores in your life that are predictable, repeatable, and chronically deferred. CME compilation. CV updates. Newsletter scrapes. A faculty admin digest. Each of those is a Scheduled Task waiting to happen.
Use cases — leaning clinical and academic
Monthly CME compiler. Forward CME confirmations to a labeled email folder; drag certificates into one Drive folder. First of every month, Cowork organizes them into a tracked spreadsheet with credits, dates, accreditation, and a printable summary.
CV self-updater. Once a month, Cowork searches PubMed for your name, finds new DOIs, and appends them — formatted to your existing CV style — to your living .docx. Residents and students forward citations to a dedicated address; those go in too.
Weekly clinic schedule scrub. Once a week, scrape your forwarded clinic schedule for next week’s day-of-surgery cases, flag prior-auth gaps, missing imaging, and patients who never confirmed pre-op visits. Output: an HTML you read with coffee Sunday night. (Avoid PHI — use de-identified scheduling exports.)
Orthopaedic trauma academic digest. Every Monday at 5am, scrape the latest issues of JBJS, JOT, OTA Highlights, and a curated PubMed query for ortho trauma. Output: a Techy-Surgeon-branded HTML digest with abstracts, your personal “interesting/skip” tags, and links to full text.
Weekly team memo draft. Friday afternoon, Cowork builds a draft team memo from your Granola transcripts, Slack activity, and HubSpot wins/losses. Lands in your inbox as an editable email — you ship it Monday morning with light edits.
Family inbox tidy-up. Every Saturday at 7am: a digest of school emails, sports schedules, RSVPs needed, and bills due. One scannable dashboard for the whole household — a quiet upgrade to weekend coordination.
Quarterly faculty dossier refresh. End of every quarter, refresh a dossier folder: updated CV, talks given, talks invited, mentees and their wins, grants in flight. Promotion-and-tenure preparation becomes a non-event.
Coach client digest (the future state). For life coaches and exercise coaches: when client-side MCPs (e.g., a health connector) mature, pipe weekly client emails or activity summaries into one Sunday-night dashboard you bring to Monday calls.
How to set one up
Open Cowork → invoke the Schedule capability. Just click the schedule button in left sidebar.
Describe the task as if it’s a one-shot: inputs, sources, output format, where to save.
Set the cadence (daily / weekly / monthly) and a time of day.
Choose delivery: file written to your workspace, an HTML artifact, or an email to yourself.
Let it run once manually. Audit the output. Then set it free.
Mode 03 — Live Artifacts: The Small Command Center
A Live Artifact is the newest of the three primitives. It’s a self-contained HTML page that persists across sessions and, when you re-open it, queries your connectors fresh — Gmail, HubSpot, Granola, Slack, calendar, Notion, and so on. Think of it as a tiny, purpose-built dashboard that you treat like a website.
It’s been a little clunky in earlier iterations — be honest about that — but its leverage scales directly with how many connectors you’ve authorized. With three connectors it’s a notepad. With ten, it’s a command center.
Use cases — built for connector-rich operators
Founder’s morning command center. One page that, when re-opened, shows: emails awaiting reply, hot HubSpot deals, this week’s Granola decisions, open Slack threads waiting on me. The thing I check before standup.
Health-tech news radar. A live page that on re-open scrapes the day’s headlines from a curated set of health-tech outlets. Not on a schedule — available when I want it. Great between cases, terrible to schedule daily.
Mentee + abstract tracker. A panel of every resident/student you mentor, what they’re working on, last touchpoint, abstracts in flight, deadlines next 30 days. Rebuilds itself from the connected Notion + Gmail every time you open it.
Slack pulse — company-wide. If you’ve trained your team to post updates in specific channels, a Live Artifact can pull a snapshot of the last 48 hours — “what’s on fire, what’s shipping, what’s quiet.” A high-leverage CEO ritual.
Family logistics page. Calendar conflicts next 7 days, kids’ school emails needing reply, household chore status. A page my wife and I both can refresh on Sunday night — the new fridge whiteboard.
Live grant + RFP scanner. Pulls active NIH/AHRQ/PCORI postings against your saved keywords and shows the next 14-day window. Perfect for a research office; useless on a schedule because deadlines move.
How to spin one up
In Cowork, ask Claude to create a Live Artifact with the panels you want.
Specify which connectors it should query (Gmail, Granola, HubSpot, Calendar, Notion, Slack, etc.) and what each panel should show.
Cowork drafts the HTML and tests the connector calls — review the first render carefully.
Pin the artifact in the sidebar. Re-open whenever you want a fresh pull.
Iterate the prompt as your needs change — add panels, remove noise, retune queries.
“Live Artifacts feel like a tiny private Bloomberg terminal — but tuned to your specific job, not the market’s.”
Decision Tree — Which One Do I Use, Right Now?
Answer one question, then look at the answer:
“Is this a one-time thing, a recurring thing, or a thing I want to glance at?”
One-time, big. You want a deliverable while you’re away. Your desktop is on. Files matter. → Dispatch.
Recurring. Same job, predictable rhythm, low surprise. You want to forget about it. → Scheduled Task.
Glance-able. You want a page that re-renders from your connectors when you open it. → Live Artifact.
Watch out for these mismatches
Don’t schedule what should be live. If the data changes faster than your cadence, a schedule will deliver stale snapshots. Health-tech news is a bad daily schedule (it’s stale by lunch) but a great Live Artifact.
Don’t dispatch what should be a chat. If the task is short and you’ll iterate on it, dispatch is overkill — you spend more time briefing than the task takes. Save dispatch for projects that take Cowork 10+ minutes of work.
Don’t make a Live Artifact you’ll never re-open. Live Artifacts chew up tokens through repeated openings. If you’ll look once and forget it, just answer in chat.
Field Notes — Pitfalls I’ve Learned the Hard Way
None of these modes are magic. They depend on a small number of preconditions that are easy to forget. And when one breaks, the failure lingers quietly in your workspace. Two minutes of awareness up front saves a frustrating “wait, why didn’t that run?” later.
Dispatch — the “approval prompt” problem. Cowork will sometimes pause a Dispatch to ask a clarifying question or approve a step. If you can clear it from your phone, fine, but if you go offline (airplane mode, scrubbed in, dead zone), the task sits and waits/never gets deployed. Lesson: brief tightly enough that approvals are rare, and glance at the phone whenever you can to clear any prompts. OR set approve all on Claude but this is a more dangerous path.
Scheduled Task — the “laptop is closed” problem. Scheduled Tasks run on your machine. If the laptop is off, asleep with the lid closed, or out of battery at 5am, the schedule simply doesn’t fire. Lesson: keep the device plugged in and awake overnight on the days a critical schedule runs, or move it to a dedicated always-on machine like a Mac Mini if you fancy.
Connectors — the “stale connector” problem. If you change a password, rotate an MFA token, or revoke an OAuth grant, the connector goes silent without throwing a loud error. Your scheduled CV update will produce nothing useful. Lesson: after any password change, do a 60-second sweep of the connector panel and re-authorize anything red.
All modes — the “context drift” problem. A schedule you set up in February may produce nonsense in October because your priorities, sources, or folder structure changed. Lesson: audit each scheduled task quarterly — read one of its outputs end-to-end and ask whether it still earns its slot.
Live Artifact — the “I forgot it exists” problem. Live Artifacts only pay rent when you re-open them. If a panel falls out of your daily ritual, it’s a bookmark you’ll never click. Lesson: pin only what you’d genuinely check, and prune the rest.
Dispatch — the “scope drift” problem. Big dispatched tasks tend to drift if the brief is loose (”triage everything, draft replies, summarize, build a deck…”). The longer the surface, the more interpretation Cowork has to do. Lesson: scope dispatch tightly, even if you have to break a big idea into two dispatches back to back.
A useful reframe: treat these tools like a thoughtful but new team member. They will do exactly what you asked. The discipline is in the brief, the connector hygiene, and the periodic audit.
If you still feel like you are having trouble getting started, all of the use cases suggested in this article are accessible below in word documents and copy pastable prompts. Enjoy!
The starter kit — for paid subscribers
Below , I’ve assembled a ten-prompt starter kit covering the use cases in this article. Four Dispatches, four Scheduled Tasks, two Live Artifacts. The Dispatches sit inline below, copy-paste blocks you grab from your phone or laptop and drop into a fresh Cowork chat. The Scheduled Tasks and Live Artifacts ship as a single Techy Surgeon-branded PDF, designed to be a reference you keep, customize, and revisit as your context evolves.
