Something quietly changed in Claude Cowork over the last few weeks that most people are sleeping on. Claude can now use your computer. Not metaphorically — literally. With computer use rolling out to Pro and Max users, you can step away from your desk, message Claude from your phone, and come back to find it opened apps, navigated websites, filled spreadsheets, and finished the work you described. Pair that with the other March release — scheduled tasks — and you have something genuinely new: an AI that runs recurring jobs on autopilot.
Computer Use: What Changed
Before this update, Cowork was already powerful for file work — synthesizing documents, reorganizing folders, building spreadsheets. But everything happened inside Claude Desktop working with local files. Computer use opens the whole machine. Claude can now open apps on your Mac or Windows machine, navigate a browser and fill in forms, read what's on screen, and execute multi-step cross-app tasks end to end. The canonical example Anthropic showcased: analyze data in Excel, then build a PowerPoint from those findings — no copy-pasting, no restarting. Key constraint: computer use only works when your desktop is running and Claude Desktop is open. It's not a cloud agent — it's genuinely using your machine.
Scheduled Tasks: Set It and Forget It
Scheduled tasks launched the same month and are arguably even bigger for day-to-day usefulness. You write a prompt once, pick a cadence (daily, weekly, monthly), and Cowork runs it automatically — no API, no code. Smart detail: after the first run, Claude rewrites the prompt itself, baking in what it learned (where files live, which connectors to use, what outputs look like). Great starting uses: daily briefing pulling emails + calendar into a morning summary; weekly report compiling connected tool data into a Google Doc; Friday file cleanup organizing work from the week. The catch: your machine needs to be awake and Claude Desktop open when the task runs. If not, it fires the next time you open the app.
Tip of the Week: Write Scheduled Task Prompts That Actually Work
Treat it like leaving instructions for someone who has never done this job before — not a description of what you want, but a complete briefing on how to do it. Here's the difference:
❌ Weak
Summarize my emails from the past week.✅ Strong
Check my Gmail inbox for emails from the past 7 days. Ignore newsletters. For each real email: sender, subject, one-sentence summary, action required. Format as markdown table. Save as Weekly Email Summary [date].md in /Reports/Weekly in Google Drive.After the first run, Claude rewrites the prompt itself — so your investment in specificity compounds.
Worth Reading This Week
- → Put Claude on Autopilot: /loop and /schedule Built-in Skills — Solid walkthrough of scheduling from Rick Hightower. The /schedule skill pattern is a genuinely useful shortcut for recurring work.
- → Claude Cowork Setup Guide: Context, Instructions, Plugins, Workflows — If you haven't done a proper setup pass yet, this is the best single guide. Covers the Customize menu, how to structure your workspace, and plugin installation.
- → I Connected Claude to Notion, Slack, and Gmail for 6 Weeks — Real long-term connector use with honest takes on what actually saves time versus what sounds better in theory.
- → Schedule Recurring Tasks in Cowork — Official Docs — The official help article. Short and useful, especially the section on what happens when your machine is asleep.
Computer use and scheduled tasks are both live now. The pattern that's emerging: the real power is in combining them. Run tasks on a schedule, let Claude use your computer to finish them, and you've built a background assistant that handles work without you having to click.
Until next time.
— The ClaudeCowork.com team