AI Agents · Claude · Quick Guide

Three Ways Claude Can Use a Computer

Computer use, Claude in Chrome, and Claude Code. Three surfaces, one rule for picking the right one.

Three Ways Claude Can Use a Computer

Many people use Claude like a smarter search box: ask, read, copy, paste, repeat. The marketers pulling ahead use it as a smart computer: open the dashboards, read the numbers, write the report. That hour you spend stitching together a weekly recap? Handed off.

Claude does that three ways. Prefer a structured tool (an MCP server, a CLI, an API, or a connector) whenever one exists. Reach for visual control only at the boundary where structured tools stop. (If you’re still pasting prompts into a chat window, wire up these five connectors first.)

Quick pick

Use the most structured option that can do the job. APIs, MCP servers, CLIs, and connectors are faster and more reliable than running in a browser via visual control. Use browser or screen control when the work lives behind an old user interface and there is no better way to connect.

Quick pick comparison for Claude Code, Claude in Chrome, and computer use

Decision flow

Decision flow for choosing a structured connector, Claude in Chrome, Claude Code, or computer use

1. Computer use: the tool (the whole screen)

Through the computer use tool in the Claude API, Claude operates a computer the way a person does: it reads a screenshot, moves the cursor, clicks, and types. It works on any GUI, even software that was never built to be automated and apps that ship with no API at all.

You know the no-API portal that eats your Monday: the regional ad network, the co-op reimbursement system, the vendor dashboard from 2014. This is the option that can log in and pull the numbers on a schedule, no human babysitting it. Claude already does a tamer, one-click version of this inside your spreadsheet, reading and writing the actual workbook (the $80 Excel feature that’s now $20).

  • Use it for: native or legacy desktop apps, GUI-only flows, anything without an API, recurring multi-app jobs you want to schedule.
  • Turn it on: it’s an API tool, still in beta. You build with it, usually against a sandboxed VM or container, or reach for an agent product that already has.
  • Watch out: it burns tokens, and it is the slowest and riskiest option. Put human approval in front of purchases, posts, account changes, and anything customer-facing.
Claude using screenshots, cursor movement, clicks, typing, and download actions in a vendor portal
Claude sees the portal, acts through mouse and keyboard events, then returns the result to your agent loop.

2. Claude in Chrome: your signed-in browser

A Chrome extension that lets Claude read, click, and navigate in your real browser: your tabs, your logins, working alongside you in a side panel. Same weekly-reporting win: four ad platforms behind your login, one summary, your coffee break.

  • Use it for: cross-channel ad reporting, research across authenticated sites (Sales Navigator, Apollo, your analytics), pulling a prospect list together, form-filling tied to your account.
  • Turn it on: install the Claude in Chrome extension, then hand Claude the task in the side panel. Anthropic says it is available to paid plans; the browser extension surface is still beta as of July 8, 2026.
  • Mind the boundary: the site reads Claude’s actions as yours. Anthropic ships permission prompts and site controls for exactly this. Keep sends, purchases, and posts behind your review. Your customers already half-distrust this stuff (49% use chatbots, 71% fear them). Don’t be the brand that proves them right.
Claude in Chrome comparing Meta Ads, Google Ads, and Analytics tabs from a browser side panel
Claude works inside your signed-in browser session, so it is ideal for authenticated dashboards and multi-tab research.

3. Claude Code: your machine, through the terminal

The agentic surface, and the one marketers underestimate. Claude Code runs in your terminal or IDE and operates your real machine: running commands, editing files, calling MCP tools. It also connects to Claude in Chrome to drive a browser for building and testing. It’s the tightest build-edit-debug loop of the three, and it’s how people turn one-off prompts into a workflow that runs itself.

I build landing pages this way: Claude edits the files, previews the page, and I can say “make this section first,” then watch it reload. This is the surface behind the marketers shipping their own tools in a weekend (from zero to a self-running factory with Claude Code).

  • Use it for: building and shipping pages and small tools, running a local app, automating a recurring workflow, testing what you’re building.
  • Turn it on: install Claude Code, then add the Chrome integration for browser automation when you need browser verification.
  • Watch out: it is powerful because it can edit and run things. Use git, small commits, and test commands as guardrails.
Claude Code editing files, running a local preview, and checking the hero in Chrome
Claude Code edits the files, runs the build, then uses Chrome to inspect the page like a reviewer.

Resources

Last checked: July 8, 2026.

Official (Anthropic):

Related from MarketingAlec:

What should we make next?

We’re testing a new rhythm: deeper dives on Wednesdays, practical resources on Fridays. The goal is to give you something useful while there’s still time to try it before next week gets moving.

What would you like to see more of?

Keep going.

I write about using AI for real work, minus the hype.

More at marketingalec.com →