🔥 AI UPDATE
Step-by-step setup for Cowork and Claude Code, with exact prompts and safety gates that keep automation from going sideways
Table of Contents
What Anthropic Shipped
As of the week of March 28, 2026, Anthropic's Claude can control a Mac remotely through two surfaces: Cowork (the desktop app for non-developers) and Claude Code (the CLI tool for engineers). The capability covers keyboard input, mouse clicks, scrolling, application switching, and file system navigation.
This is not browser-only. Claude can open Finder, move files, interact with native apps like Calendar, Notes, Mail, and any GUI application visible on screen. The model sees your screen, reasons about what it sees, and acts accordingly.
Claude Code users get an "auto mode" where the agent independently decides which actions are safe to execute without asking for confirmation on each step. Cowork users get a guided interface with explicit approval steps built in.
📊 Key Insight
Claude Code auto mode executes low-risk actions independently, pausing only when the next step involves irreversible changes: sending email, deleting files, or submitting forms.
Which Workflows Actually Benefit
Computer use performs best on structured, repetitive tasks with predictable screen states. It handles poorly any workflow where the UI changes unpredictably, requires CAPTCHA verification, or involves modals with dynamic content loaded by JavaScript. Avoid: bank portals, government sites, and anything with session timeouts under 5 minutes.
Ideal candidates share three traits: you do the same sequence of steps every time, the screen always looks roughly the same, and the cost of a mistake is recoverable (not permanent). With those criteria in mind, here are 5 workflows that work reliably in the first week of use.
Workflow 1: CRM Contact Log from Email Thread
After a prospect conversation, most operators manually extract names, company, deal stage, and next step from an email thread and paste them into HubSpot or Salesforce. Claude can do this in 90 seconds. You open the thread, trigger Claude, and it reads, extracts, opens the CRM, navigates to the contact record, and pastes the update.
EXAMPLE PROMPT
I have an email thread open in Mail. Read the thread and extract: contact name, company, role, conversation summary in 2 sentences, and the agreed next step with date if mentioned. Then open HubSpot in Chrome, go to Contacts, find the person by name, and paste the summary into the Notes field. Stop before saving and show me what you plan to enter.
Time saved per contact: 8 to 12 minutes. For teams logging 10 to 15 contacts per week, that's 1.5 to 3 hours reclaimed without any API integration or custom code.
Workflow 2: Weekly Report Compilation from Spreadsheets
If your weekly reporting involves pulling numbers from multiple spreadsheets and assembling them into a summary doc or slide, this is exactly the kind of task computer use handles without complaint. Claude can navigate between open applications, copy values, and paste them into a template you've already built.
EXAMPLE PROMPT
"I have three Excel files open: Sales_March.xlsx, Support_March.xlsx, and Marketing_March.xlsx. Pull the totals from row 2 of each Sheet 1 and paste them into the Weekly_Summary_Template.docx that is also open, matching each number to the corresponding row label. Do not close any files. Stop before saving the template."
Workflow 3: Job Application Tracker Update
Recruiters and hiring managers who track candidate status across spreadsheets, email, and an ATS spend disproportionate time on status syncing. Claude can read the latest email from a candidate, determine status (replied, ghosted, scheduled, declined), open the tracker, find the row, and update the cell.
EXAMPLE PROMPT
Check my unread emails from candidates in the folder labeled 'Recruiting.' For each email, determine the candidate's current status: responded, interview scheduled, declined, or no reply. Open Candidates_Tracker.xlsx, find each candidate by name, and update the Status column. List every change you plan to make before touching the spreadsheet.
Content operators who post across LinkedIn, X, and Instagram spend 20 to 30 minutes per piece navigating compose interfaces, reformatting for platform conventions, and staging drafts. Claude can take a source post, reformat it for each platform, open each app, and paste the version into the compose window, stopping before posting.
EXAMPLE PROMPT
I have a blog post open in Notes. Reformat it as: (1) a 200-word LinkedIn post in first-person, no hashtags, ending with a question; (2) a 3-tweet X thread, punchy, starting with the key stat; (3) a 120-word Instagram caption with 5 hashtags at the end. Open each platform's compose window in Chrome, paste the matching version, and stop before publishing. Show me each version first.
Workflow 5: Invoice Data Extraction to Accounting Software
Accounts payable teams extract vendor name, invoice number, amount, and due date from PDF invoices and enter them manually into QuickBooks, Xero, or similar tools. Claude can open the PDF, extract the fields, navigate to the accounting app, and fill the entry form, pausing for approval before saving.
EXAMPLE PROMPT
I have 6 invoices as PDFs in my Downloads folder. For each one, extract: vendor name, invoice number, invoice date, due date, and total amount. Open QuickBooks in Chrome, navigate to Bills, and create a new bill entry for each invoice. Map vendor names to existing vendor records. Stop before saving each entry and show me the full entry first.
The Two Safety Gates You Must Include
Every computer use prompt needs two explicit instructions, regardless of the task:
Gate 1 — Show before submitting: "Stop before saving/sending/submitting and list what you plan to enter." This prevents irreversible actions from running without a human checkpoint.
Gate 2 — Log all actions: "Keep a running list of every action you take." When something goes wrong, the log tells you exactly where it broke and what to correct in the prompt.
🎯 Time to Production
Most operators go from first demo to a reliable automated workflow in 1 to 2 days. Document the prompt that worked and add it to your standard operating procedure. That's when the time savings compound.
Time Savings at a Glance
Workflow | Manual Time | With Computer Use | Weekly Savings |
|---|---|---|---|
CRM contact logging | 10 min/contact | 90 sec/contact | 90 min (10 contacts) |
Weekly report build | 60 min/week | 8 min/week | 52 min |
Social post staging | 25 min/post | 5 min/post | 60 min (3x/week) |
Invoice AP entry | 5 min/invoice | 45 sec/invoice | 75 min (20 invoices) |
Where to Start This Week
Pick the one workflow that costs you the most time this week. Not the most interesting one — the most expensive one in hours. Run a single demo with full human oversight, document what worked, and standardize the prompt. Ship one workflow before building a second.
Cowork users can start immediately with no setup. Claude Code users should install the latest CLI version and enable auto mode in settings before running their first session.
Get the full newsletter every week
This article is part of the PromptHacker Weekly premium deep-dive series. Subscribe to get all 7 articles plus the newsletter every Wednesday. Click here now
More from this week's issue