Computer use

Some things you can only confirm by *looking* — did the button actually move, did the upload really finish, does the app open at all. Computer use lets Claude drive a real screen: open an application, click and type through its windows, and verify the outcome visually. It's how Claude closes the loop on work that lives in a graphical app, not just in code and text.

Most of what Claude does is text and files — but plenty of real work only exists on a screen. Did the page render right? Did the form submit? Does the desktop app even launch? You can describe those things, but the honest way to know is to look. Computer use gives Claude that ability: it can open an application, move through its windows the way you would — clicking, typing, scrolling — and then see the result.

The point isn’t to replace editing files; it’s to close the loop on things only a graphical interface can confirm. Claude makes a change, then opens the app and checks it actually worked, rather than assuming. That’s especially valuable for flows that cross between code and a UI — a setting buried in a menu, a checkout that has to be walked end-to-end, a layout you can only judge by eye.

It’s more deliberate than the rest of Claude’s tools, and that’s by design: driving real software is powerful, so it moves carefully and you can watch every step. Use it where seeing is believing — and keep an eye on the screen when anything sensitive is on it.

Open the app, click through the checkout flow, and tell me if the new discount applies.

Open the settings window and turn on dark mode, then show me a screenshot.