Anthropic launched computer use for Claude this week. In plain terms, Claude can now control your Mac. It clicks, scrolls, types, opens apps, navigates browsers, and moves between windows. When it does not have a dedicated integration for something, it falls back to using the screen the way a human would.
I watched the demo and my first reaction was "this changes the economics of getting things done with AI." Because the biggest remaining bottleneck with AI tools is coverage. Yes, integrations like MCPs and plugins already let AI send emails, update spreadsheets, manage tasks, and work inside specific platforms. Those structured connections are fast and reliable. The problem is they only exist for a fraction of the software most businesses actually use. What about that internal procurement system from 2014? The industry-specific portal your team logs into every morning? The legacy CRM that has no API? Computer Use removes that coverage gap entirely. If a human can see it on screen and click through it, Claude can now do the same.
Why integration was the real blocker
Here is the thing I keep running into with clients. We identify a workflow that AI should be able to handle. We build the logic. We write the prompts. And then we hit a wall because the AI cannot actually touch the tool the team uses for that step. There is no API. There is no integration. There is no plugin. So a human still has to do that one step manually, which breaks the flow and adds time back in.
Computer use solves this in the most brute-force way possible. Instead of building a custom integration for every tool, Claude just uses the tool the way your team does. It looks at the screen, finds the button, clicks it. Is it elegant? No. Does it work? Apparently yes, well enough that Anthropic shipped it as a research preview for Pro and Max subscribers.
The implication is significant. Any software your team uses, regardless of whether it has an API or a Claude integration, is now potentially part of an AI workflow. That old internal tool with no API that everyone hates but cannot replace? Claude can use it. The niche industry software that will never build an AI integration? Claude can use that too.
The permission model matters
Anthropic built this with a permission-first approach. Claude asks before it touches a new application. You can stop it at any time. It is not quietly moving your mouse in the background while you work. You have to be in a session, assign the task, and grant access.
That is the right way to build this, especially for business use. The teams I work with need to trust that their AI tools are doing what they asked and nothing more. A permission-based system means the business owner or team lead controls exactly what Claude can and cannot do on their machine. That control is essential if you are going to let an AI loose inside your actual work environment.
What this means for the businesses I work with
Most of the small businesses I help are running something like eight to twelve different tools across their operation. Project management, email, design, accounting, social media scheduling, CRM, file storage, communication. The dream is having AI work across all of them seamlessly. Until now, that meant building integrations one by one, which is slow and expensive.
Computer use offers a shortcut. Not a perfect one, because using a screen is slower than using an API, and the feature is still early. But for the tasks that currently require a human just because no integration exists, this is a genuine step forward. It means more of the workflow can be automated, and the pieces that could not be connected before now can be.
The businesses that get ahead of this will be the ones that have already mapped their workflows and know exactly where the manual steps are. Because those manual steps are now the first candidates for computer use automation.
I help teams map those workflows and build AI into every step that makes sense. If you want to know where computer use could save your team time, here is how the fractional AI engagement works.
