When APIs Don't Exist
Computer Use closes the last gap — even GUI-only software becomes addressable.
TUTOR WITH THEFOCUS.AI
Copy this prompt into Claude, ChatGPT, or any external AI assistant. It points the assistant to the course instructions and links it to your student profile to track your progress and customize observations.
You are not enrolled yet. Enroll to generate a Student ID to track lesson completions and store learning notes.
The last mile: browser automation and Computer Use make GUI-only software automatable. Four lessons, about 35 minutes total.
Lessons in this chapter
- Browser Automation — Claude drives a real browser — DevTools MCP for precision, Claude in Chrome for everyday. (~10 min)
- The Tool Hierarchy — API first, CLI second, browser third, screen last — and why. (~5 min)
- Computer Use — If a human can click it, Claude can click it. (~10 min)
- The Last Mile, From Your Phone — Dispatch GUI work from anywhere — with a human gate where it counts. (~10 min)
If you take five things from this chapter
1. Follow the hierarchy ruthlessly: API/MCP first, CLI second, browser automation third, screen control last. Never pixel-click what you can API-call.
2. Claude in Chrome for everyday errands, Chrome DevTools MCP for precision. Both beat Computer Use for anything with a web page.
3. Retire the "no API" excuse. Legacy tools, vendor portals, 20-year-old desktop apps — if a human can click it, it's automatable. Budget it as slower, and watch it work.
4. Mix levels inside one task. Read the PDF natively, apply the skill, enter data via the browser — use the highest level available for each step.
5. Keep a human between the agent and money. Flag-and-approve beats fully autonomous anywhere payments, orders, or filings move.
That completes Depth 3. Before the production chapters, take the Delegation Review — ten questions across Chapters 06-08.