Let Claude Use Your Windows Apps, With You Approving Risky Steps

Claude Code is very good at anything a terminal can reach. A lot of real work isn't in a terminal, though: installers, settings dialogs, desktop apps you're building, admin tools with no command line. This post explains what it looks like to let Claude use your Windows apps, how to watch the screen live from your phone, why risky steps pause for your approval, and which tasks are worth handing over versus keeping for yourself.

What desktop control adds beyond the terminal

In a terminal, Claude can read and edit files, run commands and check their output. That covers most coding work. It stops at the edge of anything that only has a graphical interface:

• An installer wizard with no silent-install flag.
• A setting buried three dialogs deep in a Windows control panel.
• The desktop app you're building, where the question is "does this window actually look right?"
• An internal tool or vendor app that only exists as a GUI.
• A flow in a browser that needs a real click through.

Desktop control closes that gap. With Coder IDE on a Windows computer, Claude can open apps, click and type when you ask it to from your phone. You stay in the loop the whole time, both by seeing the screen and by approving the steps that matter.

Desktop control is for the parts of a task the terminal can't reach. It isn't a replacement for doing things in code when code can do them.

See your Windows screen live from your phone

The first piece is visibility. Coder IDE gives you a live view of your Windows computer's screen from your phone or any browser, on any monitor if you have more than one. You can switch between monitors to follow what's happening.

That's useful on its own, without Claude involved:

• Check whether a long build or render finished.
• See an error dialog that a remote terminal would never show you.
• Confirm the app you just changed actually opened.

With Claude working on the desktop, the live view is how you supervise. You watch the cursor move and the windows change, in the same way you'd look over someone's shoulder.

It also changes how much you need to trust a summary. When an agent only reports back in text, "I changed the setting" is all you have to go on. With the screen in front of you, you can see the setting changed, see the app relaunch, and spot the moment something looks off before it goes any further. That's the difference between reviewing a result and supervising a process, and for GUI work the second is usually what you want.

Risky steps wait for your approval

Clicking around a real desktop is more consequential than editing a file in a git repository. There's no git reset for a dialog you confirmed or a setting you changed. So when Claude works on your Windows desktop, risky steps wait for your approval instead of running straight away.

The approval works the same way as Claude Code's other permission requests in Coder IDE:

1. You get a push notification that a session needs your approval.
2. You open it on your phone or in a browser and see the full request.
3. You approve or deny it. If you deny, you can reply with what you'd rather Claude do.

Because you can also have the live screen view open, you're not approving blind. You can see exactly which window Claude is in before you let it continue. If you want the general pattern for handling approvals from a phone, approving Claude Code permission prompts from your phone covers it.

Good first tasks

Start with tasks where a mistake is cheap and the result is easy to check on screen:

• Checking your own desktop app. After a code change, ask Claude to launch the app, open the screen you changed and describe what it sees. You watch along in the live view.
• Reproducing a GUI bug. Give Claude the steps from a bug report and have it walk through them, so you can see whether the bug still happens.
• Working through an installer. Next, next, accept, choose a folder: tedious for you, simple for Claude, and you can see every screen.
• Finding a setting. "Turn on developer mode" or "show file extensions in Explorer" is a good test of navigating Windows settings.
• Gathering information from a GUI tool. Read a value out of a program that has no export or command line.

Each of these has a clear end state you can verify by looking. That's the right shape for a first try.

What to keep manual

Some things shouldn't be delegated, however good the agent is:

• Passwords, two-factor codes and sign-ins. Type them yourself.
• Money. Purchases, banking, billing pages.
• Sending things to people. Emails, chat messages, posts. Once sent, it's sent.
• Production systems. Admin consoles for live services, deploy buttons, database tools pointed at real data.
• Anything you couldn't undo. Uninstalling software you rely on, deleting folders, resetting settings.

Approval prompts are a safety net, not a reason to hand over these tasks. If you'd hesitate to let a new colleague do it unsupervised on your computer, do it yourself.

How this compares to other tools

It helps to be clear about what other tools do, because some may fit you better.

If all you need is to take over your own mouse and keyboard remotely, a dedicated remote desktop app is built for that and does it well. Desktop control in Coder IDE is about letting Claude do the clicking while you watch and approve.

Setting it up on Windows

The screen view and desktop control work on Windows computers. Coder IDE itself also runs on macOS, Linux and WSL, where you get the editor and Claude Code sessions but not the screen view or desktop control.

1. Install Coder IDE on your Windows computer with the one command shown on your dashboard.
2. Click Sign in in the desktop app and confirm the code from a browser you're signed in to.
3. Approve the new computer. The approval shows which computer is asking and warns you if it's on a different network.
4. Open the computer from your phone or browser to see its screen live, and ask Claude to do something from a session.

Keep the computer awake while you're using it remotely. If you ever lose the phone or stop using a device, remove it from your dashboard and its access stops working immediately. More on how connections and approvals work is in the security overview.

Wrap-up

Letting Claude use your Windows apps fills the gap between what a terminal can do and what your work actually needs: installers, settings, GUI-only tools and the desktop apps you're building. The live screen view lets you see what Claude is doing, and risky steps wait for you to approve them from your phone or a browser. Start with small tasks you can check on screen, and keep passwords, payments and anything irreversible for yourself.

Start free. The free plan covers one computer, so your Windows PC is enough to try it.