Lesson 05 · Claude Mastery Pro ~13 min read 3 workflows + safety patterns

Computer use: Claude takes the wheel.

Claude's computer-use feature lets it actually click, type, and navigate web pages on your behalf. It's the closest thing to an autonomous agent that ships in a consumer product today. This lesson covers what it does well, what it does poorly, and the safety patterns that prevent disaster.

The mental model

Computer use is powerful and dangerous. Use it for boring, repeatable, low-stakes work.

Claude can navigate websites, fill out forms, click buttons, extract data. It's NOT yet good at: anything requiring login to sensitive accounts, financial transactions, or tasks where one wrong click matters. Stay in the safe zone until the capability matures.

Safety first

Never give computer use access to anything you wouldn't let a curious intern use. Banking, healthcare logins, anything with PII. Use it on throwaway browsers, throwaway accounts, public data. The capability is real; the trust required is still being earned.

Workflow 01 Data extraction from many web pages

1

The web-scraper that doesn't require you to code

Tell Claude to visit a list of URLs and extract structured data.

The prompt that works

Extraction promptVisit each of these 20 company About pages. Extract: founding year, HQ city, employee count if listed. Return as a CSV.

Best use cases

  • Competitive intelligence (visiting many competitor sites)
  • Building target lists from directories
  • Extracting data from sites without APIs
  • Periodic monitoring of pages you care about
Sites with anti-bot protection will block Claude. Sites with logins behind them won't work. CAPTCHAs will stop it. Use public, no-login data.
Time savings: Hours of manual copy-paste → minutes of supervised automation.

Workflow 02 Form filling at scale

2

Fill 50 forms without breaking your hand

Give Claude a CSV and a form URL. It fills the form, submits, moves to the next row.

The prompt that works

Bulk form promptFor each row in this CSV, navigate to [form URL], fill in the fields with the matching data, submit, and report success or failure.

Best use cases

  • Bulk submissions to directories or marketplaces
  • Onboarding tasks that require many similar form fills
  • Survey or research data entry
  • Migrating data from spreadsheets to legacy systems
Always test on 2-3 entries before letting it run on hundreds. Always have a stop button. Always check what gets submitted.
Time savings: Manual form filling for hours → automated for the boring parts.

Workflow 03 Browser-based workflows you can't easily script

3

Automate the things that only exist in a browser

Some workflows have no API, no automation, no shortcut — only a web UI. Computer use is the answer for those.

The prompt that works

Workflow examplesDaily: check 5 specific dashboard URLs for changes, summarize anything new. Weekly: visit our 3 vendor portals, download the latest invoices, save to a folder. Monthly: audit our 30 SaaS subscriptions by visiting each settings page.

Best use cases

  • Vendor portal automation (downloading invoices, etc.)
  • Internal dashboard monitoring
  • Periodic audits of accounts/subscriptions
  • Anywhere you click the same buttons in the same order routinely
These workflows often break when sites update their UI. Build them, test them, but expect periodic maintenance. Not 'set and forget' yet.
Time savings: Boring weekly routines: automated.

Final challenge: find one task to delegate

Identify one boring web task you do routinely. Test computer use on it. Start with one run; supervise; verify; then automate the routine. Most users find at least one 30-min/week task they can delegate.

What you can do now

  • Understand what computer use does well vs. poorly today
  • Apply safety patterns (throwaway accounts, supervised first runs)
  • Use computer use for data extraction and form filling at scale
  • Recognize when an API would be better than browser automation
  • Maintain automated workflows when sites change
Pro+
Up next in Claude Mastery

Lesson 6 · Claude Code: the CLI tool for serious development

Setting up Claude Code, prompt patterns that actually ship code, MCP servers, hooks. The tool that turned vibe-coding into a real workflow. See pricing →