Remotely Controlling Windows with AI from a Mac—Combining Claude Code and Remote Desktop

My usual development environment is a Mac, but work recently required me to use Windows.

This was more frustrating than it might sound. Macs and Windows PCs have different keyboard layouts and shortcuts. After not using Windows for nearly a year, I had even forgotten how to copy and paste.

So I decided to use Claude Code’s Remote Control to operate Windows from my Mac.

Operating Claude Code on Windows from a Mac

First, I installed Claude Code on Windows and enabled Remote Control.

By connecting to the remote session from my Mac, I could give instructions to Claude Code running on Windows.

I also configured MCP and other tools on the Windows side so that Claude Code could perform as many tasks as possible.

It could handle many tasks—including working with files on Windows, editing configuration files, and conducting various kinds of research—simply by following instructions sent from my Mac.

The basic arrangement was simple: I gave instructions from my Mac, and Claude Code did the work on Windows. That was all it took.

The Permission Barrier I Still Could Not Cross

However, it could not perform every operation.

Even after I configured MCP and granted as much access as possible, some commands—such as operations requiring administrator privileges—were stopped by safeguards.

I therefore decided to use Remote Desktop only for the operations that Claude Code could not perform.

Even then, I wanted to keep the work done directly on Windows as simple as possible.

So I left a PowerShell window open on Windows in advance.

I had Claude Code generate the necessary PowerShell command on my Mac, then simply pasted it into PowerShell through Remote Desktop and ran it.

The trick is to ask for a single command that completes the entire operation, since it will be copied and pasted.

Pop-up windows still appear occasionally, and when they do, there is no choice but to click OK through Remote Desktop.

In other words, I leave routine work to Claude Code and use Remote Desktop only when an execution restriction gets in the way.

Even Error Analysis Can Be Completed Entirely on the Mac

Using Remote Desktop alongside Claude Code made me realize how efficient this setup could be for debugging.

Suppose I run a command on Windows and it produces an error.

Normally, I would need to copy the error message and give it to Claude Code on Windows.

But after not using Windows for nearly a year, even copying and pasting can be confusing. I have completely forgotten shortcuts such as the one for taking a screenshot.

That is where Remote Desktop on the Mac becomes useful.

I can capture the remote Windows screen with the Mac’s screenshot function and give the image to Claude on the Mac. Claude can analyze the error and, if necessary, tell Claude Code on Windows what to do next.

I can debug an error that occurred on Windows entirely from my Mac, without having to remember how to operate Windows.

The Mac Is the Command Center; Windows Is the Work Machine

In the end, I arrived at the following division of roles:

• Mac: The command center. I use it to give instructions to Claude Code, review the work, and capture and analyze error screens.
• Windows: The work machine. Claude Code on Windows receives instructions and directly performs whatever tasks it can.
• Remote Desktop: I use it to manually run the few commands that Claude Code cannot execute and to check error screens.

Most tasks can be completed through Remote Control. Remote Desktop is a supporting tool for situations involving permission issues.

Because the Windows screen is displayed on the Mac, I can also take screenshots using familiar Mac controls.

Turning Another PC into a Dedicated Computing Machine

This setup could also be adapted to use the Windows PC as an independent work machine.

For example, I could issue instructions from my Mac and have the Windows machine perform data analysis or time-consuming computations.

I could continue with other work on my Mac while leaving the heavy processing to Windows. As far as possible, Claude Code on the Mac could also check the results and analyze any errors.

I would like to experiment with this kind of setup in the future.

Windows Is Working, but I Do Not Move from My Mac

This setup is not fully automated. There are still situations, such as operations requiring administrator privileges, in which human intervention is unavoidable.

However, I can handle most tasks simply by issuing instructions from my Mac. If an error occurs, I can capture the screen on the Mac and give the image to Claude.

The important point is not remotely controlling Windows itself. It is minimizing how much Windows-specific interaction I need to remember.

I introduced AI to help me operate Windows, and the result is that I can now get my work done even after forgetting how to use Windows. In its own way, that is a genuine technological innovation.