Big Idea

The argument in one line.

Computer Use turns any app with a visible interface into an automation target, bypassing the API-or-nothing ceiling that has blocked every legacy software integration until now.

Who This Is For

Read if. Skip if.

READ IF YOU ARE…

You run a service business or AI agency and want to automate workflows inside apps that have no API or Zapier connector.
You already use Claude regularly and want to understand what Computer Use can and cannot replace in your current stack.
You manage client automations involving legacy or proprietary software with no webhook support.
You want a realistic, limitation-honest breakdown before committing to a feature still in research preview.

SKIP IF…

You are on a Teams or Enterprise plan since Computer Use is not available there yet due to audit log gaps.
You are on Windows since this feature is Mac-only at the time of recording.
You want a deep technical dive into how screen-control AI works at the model level.

TL;DR

The full version, fast.

Computer Use lets Claude take screenshots and physically control your mouse and keyboard, giving it access to any app with a GUI. Claude dispatches tasks through a three-tier hierarchy: native connectors first, Chrome extension second, screen control as a last resort, which keeps token costs down. Paired with Dispatch, you can text tasks from your phone and have them execute on your desktop while you are away. The feature is a research preview, Mac-only, and excludes browsers and financial apps for security reasons.

Members feature

Chat with this breakdown.

Modern Creator members can chat with any breakdown — ask for the hook, quote a framework, find the exact transcript moment. Unlocks at T2: refer 3 friends + add your own API key.

Create a free account →

Chapters

Where the time goes.

00:00 – 00:37

01 · Hook and capability overview

Introduces Computer Use and Dispatch, names what the feature does, teases live demos and use cases.

00:38 – 01:10

02 · How Computer Use picks its method

Explains the three-tier dispatch order: native connector then Chrome extension then screen control as last resort.

01:11 – 02:30

03 · Setup walkthrough

Shows how to enable Computer Use in Claude desktop settings and enable Keep Computer Awake.

02:31 – 04:41

04 · Demo 1: PDF to Gmail and Slack

Prompts Claude to find a client proposal PDF and send it via email and Slack DM. Claude uses connectors rather than screen control for both, demonstrating the fallback hierarchy.

04:42 – 05:57

05 · Dispatch setup and phone demo

Shows pairing Claude mobile app via QR code, then sends a task from phone to desktop to create a notes summary from Google Calendar.

05:58 – 08:40

06 · Five practical use cases

Illustrated slide covers client deliverable prep, overnight code reviews with scheduled tasks, legacy software with no API, competitive research on autopilot, and instant case study retrieval during sales calls.

08:41 – 10:41

07 · Limitations and disclaimers

Illustrated slide: research preview status, Mac-only, browser exclusion for security, financial app blocks, sandbox breakout risk, Pro and Max plan restriction.

10:42 – 12:06

08 · Where this is headed and CTA

Frames Computer Use as a shift from AI-that-writes to AI-that-works, pitches newsletter and live workshop.

Atomic Insights

Lines worth screenshotting.

Claude uses screen control only as a last resort, checking native connectors then the Chrome extension first, which keeps token cost and error rate lower than pure screen scraping.
Any app with a visible GUI is now a potential automation target, including legacy dental and accounting software built 15 years ago with zero API documentation.
Browsers are blocked from screen control by design because web pages can embed hidden instructions that trick an AI agent into unintended actions.
Dispatch creates an async loop: text a task from your phone, walk away, come back to it done on your desktop.
Computer Use runs outside the normal sandbox and interacts with your actual desktop, comparable to granting someone remote desktop access.
Financial and crypto apps are blocked by default and you can add any additional app to the blocklist yourself.
The feature is Pro and Max only because audit logs do not capture Computer Use activity, making it unsuitable for enterprise compliance requirements.
Overnight scheduled code reviews become possible by combining Claude Code scheduling with Computer Use so it screenshots bugs and commits a report before you wake up.
A competitive pricing research task that would take a VA 30 minutes can now run on a daily automated schedule with no human involvement.
Retrieving a case study file via Dispatch during a live sales call is the use case the creator said he uses most in practice.

Takeaway

GUI access is the new API for AI automation.

WHAT TO LEARN

Every app with a visible interface is now a potential automation target, and the missing layer was never a connector but a pair of eyes and a cursor.

Claude uses screen control only as a last resort, checking native connectors then browser extensions first, which keeps token cost and error rate lower than pure screen scraping.
The legacy software unlock is the most underrated use case: dental practice management, niche accounting tools, and 15-year-old industry platforms with no API can now be automated by interacting with their GUI.
Dispatch decouples task-triggering from desk presence, letting you assign work from your phone and have it complete on your machine while you are in a meeting, at lunch, or asleep.
Overnight scheduled tasks become viable when you combine Claude Code scheduling with Computer Use, allowing QA flows to run, screenshot bugs, and commit reports to a repo before you wake up.
Computer Use breaks out of the normal sandbox and interacts with your actual desktop, so treat it like granting someone remote access rather than running a script in an isolated environment.
Browsers are deliberately excluded from screen control to prevent prompt injection attacks, where hidden text on a web page could trick the AI into taking actions the user never requested.
The practical test for whether to use Computer Use or a connector is straightforward: if the task has a native integration, use the connector every time because it is faster, cheaper, and more reliable.
The instant case study retrieval scenario of texting Dispatch to find a file during a live sales call is the kind of real-time leverage that makes the capability feel like a second person in the room.

Glossary

Terms worth knowing.

Computer Use: An Anthropic research-preview feature that lets Claude take screenshots and physically control a computer mouse and keyboard, enabling it to operate any desktop app regardless of whether an API exists.
Dispatch: A companion feature that pairs the Claude mobile app with your desktop session, letting you send tasks from your phone and have them execute on your computer while you are away.
Connector: A direct integration between Claude and a specific service such as Google Calendar or Gmail that is faster and cheaper than screen control because it uses an API rather than visual input.
Prompt injection: An attack where hidden instructions embedded in a web page trick an AI agent into performing actions the user never requested, which is why browsers are excluded from Computer Use screen control.
OpenClaw: An existing open-source tool for AI-driven computer control that Computer Use is positioned as a direct alternative to.

Quotables

Lines you could clip.

01:25

“It's not just using screen control for everything because that would be a little bit more expensive, so it's actually being optimal.”

Crisp explanation of the cost-conscious design decision with no setup needed→ TikTok hook↗ Tweet quote

10:14

“You basically have a digital employee that is always on for you.”

One-sentence value prop, punchy and standalone→ IG reel cold open↗ Tweet quote

07:35

“There's no Zapier connector, there's no webhook, there's no API documentation, there's nothing. But those apps, they do have a GUI and now Claude can interact with that GUI.”

Builds tension then resolves it cleanly, strongest articulation of the legacy software unlock→ newsletter pull-quote↗ Tweet quote

The Script

Word for word.

metaphoranalogy

00:00Yet again, Anthropic just dropped another feature that I think a lot of people have been waiting for. Now Cloud Code, it can now control your actual computer, your mouse, your keyboard, your screen. It will take screenshots.

00:10It'll figure out what is on your display, and those just click around and actually do things for you. Now, will work in both Cloud Code and Cloud Cowork and it's available right now for any Pro and Max users on Mac. But here's where it actually gets interesting is that you can pair this with another feature called dispatch, which this will let you text Claude from your phone and it will do the work on your computer while you're away.

00:29So let's say you're sitting down for lunch, you realize you forgot to export that report, you text Claude, it opens up the app, grabs the file, sends it off. So today, I'm going to be showing you guys how to actually set this up, walk you through some real demos, talk about what it is actually good at, what it can't do yet, and a few use cases that I think are going to be really practical for anyone running a business or just doing any sort of knowledge work.

00:51So let's get into it. But here's the official blog post from Anthropic. They're calling this Computer Use and it just went live yesterday as a research preview.

00:57Now what's actually happening under the hood, it's pretty straightforward. So when you tell Claude to do something on your computer, it will follow a specific order. So first, it'll check if there's a direct integration.

01:05Like, if you ask it to check your calendar, it'll just use Google Calendar Connector because that is faster and it's more reliable. Second is if the task needs a browser, it'll just use the Claude in Chrome extension. And third, when neither of those can actually handle a job, does it fall back to actually controlling your screen?

01:22So taking screenshots, moving the mouse, clicking buttons, typing, all that stuff. So it's not just using screen control for everything because that would be a little bit more expensive, so it's actually being optimal.

01:32So that's just a design choice screen control. It would be the backup option for things like any native apps, internal tools or anything that just does not have a native API integration. So So to actually turn this on, you just need to simply go into your Claude settings.

01:45So I'm on the Claude app currently. So we'll just navigate over to our settings, and from here, we'll just scroll down to the desktop app section.

01:53If you go to general and you scroll down, you should see computer use. You just have to enable this. So it's going to give you a few disclaimers, all that sorts of stuff, and we'll just enable this.

02:02What I also wanna do is going to keep our computer awake. This is going to allow us to make sure that, you know, our computer isn't going to go idle or anything so we can actually use our Cloud Code instance on the go and it's not gonna go to sleep or anything like that. Now if you're not seeing computer use, all you wanna do, just close out your application.

02:18So again, I am using this inside of the desktop app and what you wanna do, just log back out, log back in, make sure you're updated on the latest instance and you should be good to go. You'll be able to see it. Alright.

02:29Let me show you what this actually looks like. So I have this PDF. This is just sitting in my downloads folder on my computer and I want Claude to actually be able to send it as a DM to somebody on Slack, also be able to email it off to somebody.

02:39Now I don't have either of those applications open right now, I'm just going to go back to Claudia. I'm gonna say use computer use to find the client proposal PDF on my computer and send it as an email to this guy and DM it to k shav in Slack of a summary. So we'll run this off.

02:54Now it is worth noting, if you are running this for the first time using computer use for the first time, it is going to require and request a few different permissions. So if you're, you know, asking it to access your downloads, access your local computer, you will have to first provide it with those permissions. So if you're asking it to go ahead, go on Slack or record your screen, anything like that, you have to enable those system settings.

03:17So you only have to do that once. So right now, it's asking to just read for this, so I'm going to give it permission and next up should be able to be able to actually read the entire proposal and then start sending the summaries, connects to Gmail, and also connects to Slack.

03:32Alright. I've read the proposal. It's a seventy three thousand ten week AI workflow automation engagement.

03:36Before I send anything, here's what I'll do. I'll email this guy, and then I'll send the DM over Slack. Can I proceed?

03:42I will say proceed. Let me create the Gmail draft and then send this DM to Keshav in parallel.

03:48So right now, it is just using the connector. So it's not even using computer use. So right now, it is recognizing that it already has a connector.

03:55So it's going to be a bit more efficient, bit more practical because it's going to cost less tokens to actually interact and use computer use, whereas the connector it's much easier and there's a better procedure to actually be going about this. So let's go ahead and check that.

04:09Alright. So you guys can see right here, we have the draft. Please find the client proposal for Acme Corp's operations team attached.

04:15This covers the full ten week engagement. Let me know if any revisions are needed. Now I'll just check Slack.

04:19Cool. So we could see right here, hey, k, job. Here's a quick summary of the Acme Corp client proposal I just sent over.

04:24So it's pretty much the same thing as the Gmail draft. Hypothetically, if Slack was not a connector, same with Gmail, then that is where it would be able to use computer use and actually interact. Let me show you where it's actually going to be using computer use.

04:34And before we do that, I have to introduce Dispatch. So Dispatch, this is going to allow you to actually utilize Claude from your phone while your computer is elsewhere. So if you have not set up dispatch yet, just go ahead, navigate to dispatch.

04:46It's extremely simple. You'll just have to scan a QR code or just log in to Claude on your phone and it'll be paired. It is as simple as that.

04:52It takes maybe thirty seconds to set up. So go to that now if you have not already. So what I'm going to do is I'm just going to start a new message and I'm going to paste in use computer use to actually open up my notes app on my computer and create a new note summarizing today's meetings from my Google Calendar.

05:09So let's send that off. You can see I actually ran that earlier but we should see on our computer that we will have this new request. So it's going to log that, recognize the input, you know, everything's going to be hands off.

05:20So you can see that I'm not actually controlling my computer in just a second where it'll actually open up my notes. Here, this is where my notes app is now open. It says Claude is using your computer and in a second it should input everything, you know, a summary from my Google Calendar which there it was using a Google connector.

05:37So that's just something that's natively set up inside of Claude. So right now, it's just inputting everything in here. So here I have my morning routine from eight to 08:30.

05:45This is recurring. I have my team sync at 1PM and then we have a call later in the day.

05:50So awesome. That is how we are actually utilizing the computer use. Hypothetically, if we wanted to use it from our phone, so if we're away from our desk or anything else.

05:58So beyond what I just showed you, I mean, there's a thousand different use cases that you can use this for. Lead generation, lead research, lead enrichment, whatever it may be.

06:06It doesn't have to be regarding to leads, you can use this across departments for so many different use cases. So just to expand and give you guys some ideas, first one, client deliverable prep. So let's say you're just building out an automation or a Pugenetic workflow for a client and you've got the proposal doc inside of Google Docs, you've got the scope spreadsheet in Excel and the contract PDF in your downloads folder.

06:27Now normally, you would have to spend about ten minutes just jumping between apps, copying all that information, reformatting whatever it may be, but with computer use, you can just tell Claud to pull the key numbers from the spreadsheet, open the proposal, update the figures and then attach everything to a single email draft.

06:41It will handle all the app switching automatically for you. Second is any overnight code reviews with scheduled tasks. So Claude code, it already has a scheduling feature you guys may already know about where you can just set prompts to run on a Chrome.

06:53Now, combine that with computer use, you can just set a task that runs at midnight, pulls up your staging environment in the iOS simulator and then clicks through the core user flows, screenshot anything that looks off and commits a bug report to your repo before you even wake up. Now, third, and this one is very specific to agency owners, a lot of your clients, they're going to be running proprietary softwares that has zero API access.

07:14So you can think about like old clinic, like dental practice management systems where they have local accounting tools or any niche industry platforms that were just built fifteen years ago. They're legacy systems. There's no Zapier connector, there's no webhook, there's no API documentation, there's nothing.

07:30But those apps, they do have a GUI and now Claude can interact with that GUI. So you can actually build automations around software that was previously impossible to integrate with and that opens up a whole new category of clients that you can now serve.

07:44Fourth is competitive research on autopilot. So you can schedule Cloud to open a local note taking app every single morning, pull up three or four competitor websites using the Chrome extension, screenshot their pricing pages, compile a weekly comparison doc and if you're running an agency and tracking how competitors are actually positioning, that is a task that a VA may have well taken like thirty minutes to perform.

08:05Now it runs itself. And last but not least, and again, like these are not limited to just these use cases. There's so many more that you can be using this for.

08:12So this is the one that I actually keep coming back to and what I have been using this over the past day is, let's say you're on a sales call, the prospect is asking for a case study that you know is saved somewhere on your machine. So maybe it's just a Google Slides saved on your computer. So instead of saying like, okay, let me find this after the call, you can pull it up right on the call, you can use dispatch saying, hey, I need you to find me this file and then you can present it, show it on the call because you're going to have it in seconds.

08:37You don't have to be digging and finding it. Meanwhile, Claude, it will do all that for you. Now, let's talk about some limitations of what you should know before you actually get too excited because there are some important disclaimers.

08:47So first thing, this is a research preview. It works but it is not bulletproof by any means. Like sometimes Claude, it will click the right button from what I found, sometimes it misreads the screenshot.

08:58It is early. Anthropic, they are saying that upfront and that is what I respect and appreciate about them. Second, it is Mac only right now so it will come, I'm sure, for Windows pretty soon, but for right now, it's just Mac.

09:10And third, this is a big one, browsers are very limited. You can't use Google Chrome, Claude can't click around, type in Safari, Chrome or any browser through screen control. That is a deliberate security decision.

09:21So like web pages, they can contain hidden instructions that could trick an AI agent into doing something that you did not ask for. So for any browser tasks, you would have to use the Claude and Chrome extension instead, which is a separate tool or you could just download a different browser. So I don't know all the other ones available, but it will not be Chrome, it will not be Safari.

09:41All the big ones, you'll have to look for a different third party application, a different browser that you will have to use. Fourth is the financial apps and crypto wallets. These are blocked by default.

09:51So you can just add your own apps to the block list and I mean this makes sense, like you do not want an AI agent to be accidentally clicking around your training platform or your wallet. Fifth is computer use, it runs outside the normal sandbox. So usually when Claude works on files in co work, it does everything in an isolated virtual machine.

10:09But computer use, it actually breaks out of that where it's interacting with your actual desktop. So you should think of it like giving somebody remote desktop access. So you have to be intentional about what you actually let it touch and this is where it's a little bit more similar to OpenClaw and where you might want to have a different computer specifically for this so it's not going to mess up all your files or anything like that.

10:29And finally, this is only available on Pro and Max plans right now so it's not on Teams or Enterprise and the reason is that activity from computer use, it isn't captured in audit logs which is something that enterprise customers would need for compliance. Now look, I mentioned this is still early but what Anthropic just shipped here, it is pretty clear signal of where things you're actually headed to, like we're moving past the stage where AI just writes text in a chat.

10:52This is actually doing work on your computer while you can go live your life. You can pair that with dispatch from your phone and actually schedule tasks that run overnight and you basically have a digital employee that is always on for you. And for anyone running a service business or just an AI agency, this is the stuff that should be on your radar.

11:09The use cases, they're only going to get better as this moves out of the research preview. Now, if you guys do wanna stay up to date on how to actually use these tools in your business and practical AI strategies to starting and growing your business, then check out our free AI newsletter. We upload weekly sending you strategies on how when you start and actually grow your business and our experience in the space.

11:27And before you guys go, we are hosting a live free workshop next Tuesday breaking down how we use AI inside of our three companies automating about 60 to 70% of our tasks currently and how we've been implementing AI, Claude Code, Open Claw for all of our clients and the results that they have seen and how you can actually do that for yourself, your team, upscale your team and install Claude inside of your guys' environments.

11:49So if you are a business owner and you're looking to either drive leverage or increase your bottom line, then make sure to check out and sign up for that webinar next Tuesday. We'll be covering all of that.

11:58You guys do not wanna miss it. But with that being said, thank you guys for watching. Please subscribe, drop a like, drop a comment, and I'll see you guys in the next video.

The Hook

The bait, then the rug-pull.

The phrase is yet again, two words that do the job of three minutes of credentials. When Claude quietly shipped Computer Use, a feature that lets the AI physically click around your desktop and take action in any app with a visible interface, the creator had already been tracking it. Pair that with Dispatch, which lets you fire off tasks from your phone while your computer sits untouched across the room, and the demo almost sells itself.

Frameworks