The last Cowork capability changes the whole relationship. Scheduled tasks run on their own — every morning at 7, every Friday at 4. Live artifacts are dashboards that pull fresh data each time you open them. Together they turn Cowork from "a thing I open" into "a thing that delivers value while I sleep." The skill isn't setting them up — it's setting them up so they help instead of becoming noise.
Step 1 of 60% complete
The shift
From "a thing I open" to "a thing that runs"
Every other Cowork skill so far has been something you trigger. Automation is different: you set it up once and it works without you. That's powerful — and it's exactly why the failure mode is so easy to hit.
Predict first
Excited about your new 7am briefing, you think: "If a daily summary is good, an hourly one must be better." What actually happens?
Scheduled tasks
Work that's done before you sit down
A scheduled task is a recurring Cowork session that fires on a cron-like schedule. You describe what to gather and how to deliver it; it runs on time, every time.
Daily briefing · weekdays 7:00amEach weekday at 7am, look at my unread email (last 24h), today's calendar, new #leadership Slack messages, and my 3 KPI dashboards. Email me one briefing by 7:05 with: today's calendar (flag travel-time gaps), top 3 inbox priorities, notable Slack flags, and KPI status (green/yellow/red vs target). Under 300 words. No fluff.
The same shape works for a Friday-afternoon weekly recap that pulls from your CRM, GitHub, and Slack and saves a Markdown report to a folder.
Match cadence to real decision points. A daily briefing earns its place; an hourly one becomes noise you train yourself to ignore — which is exactly what you predicted a moment ago.
Do it · run the simulation
Alert on the exception, not the routine
The move that keeps automation from becoming spam is conditional logic — only act when a condition is met. Here's a real support-ticket task. Play four days: each morning, will it DM you, or stay silent?
The scheduled taskDaily 7:15am — read the ticket list. If there's any P0, DM me the top 3. Otherwise, do nothing.
Day 1 of 4 · 0 alerts fired
Live artifacts
A dashboard that refreshes itself
A scheduled task pushes you a report. A live artifact is the opposite: a saved view you pull up, and it fetches fresh data from your connectors every time it opens. Not a snapshot — a real dashboard you keep coming back to.
Live artifact · personal command centerBuild a live artifact "team-pulse" with cards for: open PRs awaiting my review (GitHub), tickets assigned to my team (Linear), pipeline by stage (CRM), recent customer feedback (Slack). Dark mode, each card a metric + small table, a reload button up top, mobile-friendly. Save it so I can open it daily without rebuilding.
When to reach for an artifact
Anything you'd otherwise check by clicking through 3–4 tools every morning: a pipeline view, a team pulse, an exec "state of things."
An artifact only refreshes what its connectors can see. Reorganize a CRM or rename a Slack channel and you'll need to update the artifact — they don't self-heal.
The discipline
Preview before you let it loose
Automation's risk is that mistakes repeat silently. A task that produces one bad report produces six before you notice. One habit prevents most of that grief.
The call
You've just built a weekly status-report task. Before you let it run every Friday on its own, what's the right move?
🤖
Cowork track complete
Cowork now works while you sleep
What you can do now
Configure scheduled tasks for briefings, recaps, and triage
Match cadence to decision points instead of over-scheduling
Use conditional logic so you're alerted on exceptions, not routine
Build live artifacts for the views you check every day
Run any task manually before scheduling — and keep auto-reports as drafts
Your move: schedule one task that runs tomorrow
Pick the recurring task that costs you the most each week — a status report, a morning briefing, a Friday recap. Build it, run it manually tonight to check the output, then schedule it. Tomorrow, see what arrives while you do nothing.
You've finished the Cowork track. The next horizon is the wider world of agents — each AI has its own: Claude Code for development, Computer Use for desktop control, plus the SDKs that let you build your own. Head back to the track to keep going.
Hey! I'm your AI Coach for this lesson on Cowork automation. Ask me about scheduled tasks, conditional alerts, live artifacts, or how to set a cadence that helps instead of spams. What do you want to automate?
Free lesson coaching is limited to 3 questions. Upgrade to Pro for unlimited coaching on every lesson.