Combining Computer Use and scheduled tasks

Complete Cowork scheduled tasks: work that runs without you first; this lesson builds on the scheduled-task pattern and adds Computer Use, so you need a working scheduled task before you combine it with on-screen action.

The most capable Cowork pattern is a scheduled task that also performs Computer Use. On a schedule, Claude opens a dashboard, reads the numbers off the screen, and delivers a formatted report on its own.

The schedule supplies the "when" and the "deliver it here." Computer Use supplies the "go operate this software and pull the numbers." Together they handle work no simple connection could, because the data lives behind a screen a person normally has to click through.

Both pieces are paid, and Computer Use is a Pro and Max research preview (Team and Enterprise plans do not have it) whose behavior can still change. This is the high point of Cowork for a non-developer, and also where you slow down, because the task now runs unattended and takes real actions.

Here is the before and after: Before, every Friday someone logs into a sales dashboard with no export button, reads the week's numbers, and types them into a summary email, a forty-minute job. With a combined task, Claude opens the dashboard, reads the numbers with Computer Use, and delivers the summary every Friday with nobody logging in.

Now try it: design the pattern on paper first. Pick a recurring report you make by reading a screen, then write down the schedule, the exact on-screen steps, and the delivery format. Build a single test run and watch it the whole way through.

Scheduled timing plus on-screen action equals work that runs itself, and that combination is exactly where you supervise the early runs most closely.

I want to design a combined Cowork task that uses both scheduling and Computer Use. I will build a test run after we design it.

Here is the situation: every Friday afternoon I log into an internal dashboard (it has no export or download option), read this week's three key numbers off the screen (total orders, total revenue, and number of refunds), and email a short summary to my manager.

Please help me design it:
1. Write the on-screen steps Computer Use would take, in order, to open the dashboard and read those three numbers.
2. Write the output format for the summary email (keep it to three labeled numbers plus a one-line note).
3. Specify the schedule and the delivery target.
4. Tell me exactly how to run it ONCE as a supervised test before I let it run on its own, and what I should watch for during that test.

Be specific. This task runs unattended later, so the test run matters.

What good looks like

• Claude lists concrete on-screen Computer Use steps (open browser, go to dashboard, locate each of the three numbers)
• The output format is specific: three labeled numbers plus a one-line note
• The schedule and delivery target are both stated clearly
• Claude gives you a supervised single test run with specific things to watch before unattended scheduling
• The design treats trust-building as a step, not an afterthought