Your Windows app connects, but the course project still needs macOS tools.
Fastest answer: Claude Code Desktop can use SSH to connect to a remote Mac from a supported Windows setup. The app is the interface on your computer; Claude Code, project files, and commands run on the remote Mac. SSH does not show or control the Mac desktop, so work that requires clicking through Xcode needs a separate graphical desktop connection. The official Desktop SSH guide describes remote sessions and host requirements.
This guide is for students who have a Windows computer and need Claude Code to work with a macOS project.
It also suits beginners who need to verify a Swift or iOS course environment before submitting work.
If the task is mainly to view a Mac screen or use Xcode windows, start by checking graphical access rather than relying on SSH alone.
Last updated October 13, 2026; platform details checked against the Desktop system requirements.
[ SECTION_01 ] Decide what kind of access the assignment needs
SSH is a secure connection for remote commands and files. Think of it as a key to a Mac’s command-line workspace, not a window into its screen. Once connected, Claude Code Desktop can work with a remote project and run commands there. The official documentation identifies remote macOS and Linux hosts as supported environments for this workflow.
Can Claude Code Desktop on Windows connect to a Mac?
Yes, if the Windows Desktop app supports the feature in the installed version and the remote Mac meets the SSH requirements. Confirm current platform availability in the Desktop system requirements. The connection is still a command-line development session, not remote screen sharing.
Use SSH when the assignment involves tasks such as:
- Reading or editing files in a project folder on the Mac.
- Running a command-line tool installed on the Mac.
- Asking Claude Code to inspect project structure or help with code changes.
- Building or testing from the terminal, when the course permits that workflow.
Choose a graphical desktop connection as well when you need to operate Xcode windows, inspect a simulator visually, or interact with another Mac application. Apple’s screen-sharing guide describes screen access as a separate function. An SSH session does not become graphical just because the app you use to start it has a visual interface.
[ SECTION_02 ] Check the host, account, and project before connecting
A remote Mac is the computer doing the work. The SSH host is its network address, like the destination written on a parcel. The account identifies which user you are allowed to access. The project directory is the folder Claude Code should work in, much like choosing the correct desk before opening your coursework.
Before opening Claude Code Desktop, confirm these details with the Mac owner, service administrator, or course staff:
- The remote host address and SSH port.
- The permitted username and authentication method.
- Whether your account can access the course project folder.
- Whether the Mac allows remote login and can reach the required development tools.
- Whether your school, network, or account policy permits remote connections.
On a Mac you administer, remote login must be enabled for SSH access. Apple’s remote login instructions explain where to review that setting. A student should not change managed school settings or work around a network restriction. Ask the administrator for an approved host and connection method instead.
Windows can use an OpenSSH client to make SSH connections. The Windows OpenSSH setup guide explains how to check or install the client and connect to a host. Claude Code Desktop may manage the session through its own interface, but knowing what the host, port, username, and key mean makes errors easier to identify.
What should you use for a student Mac programming environment?
Use the computer that meets the assignment’s actual requirements. A local Windows editor may be enough for general coding, but it cannot run Mac-only development tools locally. An approved remote Mac can provide that environment without moving your project onto an unsupported setup. If the course requires visual Xcode work, confirm screen access separately.
[ SECTION_03 ] First connection: add the SSH host in Claude Code Desktop
Open the Desktop app and locate its remote or SSH connection option. The exact labels can change between app versions, so follow the current official SSH setup steps if the screen differs. Add a host entry, then fill in the connection details supplied by the administrator.
Each field has a simple purpose:
- Host: the Mac’s network name or IP address. It tells the app where to connect.
- Port: the SSH listening port. Use the value provided by the administrator; do not guess if the host uses a non-default port.
- Username: the permitted account on the remote Mac.
- Identity file: the path to your private SSH key, if key-based authentication is required.
- Remote path: if offered, the starting location on the Mac. Choose the course project folder only after confirming its full path.
If you already use SSH on this Windows computer, Claude Code Desktop may be able to use an existing SSH configuration. Check the official instructions and your current configuration before creating a duplicate entry. Reusing a known working setup can avoid entering inconsistent host details, but do not copy settings from an account you are not authorized to use.
A private key is like a door key that proves you are allowed inside. Keep it on your own device and protect it with the security method required by your setup. Never send the private key, account password, or login credentials to another person. Do not paste them into a Claude prompt, a course submission, or a shared chat. If the app asks for a key file, select the approved file through the connection settings rather than revealing its contents.
When you start the connection, authenticate using the authorized method. The official guide states that Claude Code Desktop can install Claude Code on the remote host on first connection. That installation happens on the remote system; it does not mean the Mac’s desktop is being streamed to Windows. Review the remote installation and connection conditions before assuming the host is ready.
[ SECTION_04 ] After connecting, choose the remote project
A successful connection is not proof that the right project is open. Select the course folder on the remote Mac, not a similarly named folder on the Windows computer. Desktop is the interface on the local computer, but the project files and commands for this session are on the connected host.
Where does code run after Claude Code connects to a remote Mac?
Remote-session commands run on the Mac, and Claude Code works with the project selected there. Files in a Windows folder are not automatically the same files as those in the Mac project directory. Confirm the active path before asking Claude Code to inspect or edit anything.
Start with a harmless check. Ask Claude Code to list the project files or summarize the folder structure. Then ask it to identify the current directory and the development tools available there. These checks should not modify coursework. If the answer shows a Windows path, an unexpected home folder, or an unrelated project, stop and select the correct remote directory.
For a small first task, ask Claude Code to explain one file or suggest a limited change. Inspect the proposed changes before accepting them. If the project uses Git, review the difference with the git diff command or an equivalent interface. The Git diff reference explains how to compare working-tree changes with the project’s tracked version. A difference review helps reveal accidental edits, removed course code, or changes outside the intended file.
[ SECTION_05 ] Complete a course exercise and verify the result
A safe first exercise is a small edit with an easy check. For example, ask Claude Code to add a brief comment or adjust a simple output message in a course file. Before applying the change, confirm that the target file is part of the expected project. Afterward, review the difference and run only the command required by the assignment.
Use this sequence:
- Ask Claude Code to identify the project folder and the file it plans to change.
- Read the proposed edit and confirm it fits the assignment.
- Apply the change only after checking the target.
- Review the file difference, including any files that were added or removed.
- Run the course’s required test or build command on the remote Mac.
- Read the command output and compare it with the assignment’s acceptance criteria.
- Keep or undo the change based on what the project actually requires.
These are checks, not a guarantee that generated code is correct. Claude Code can misunderstand instructions, edit the wrong file, or produce a result that builds but fails the course requirement. The student remains responsible for understanding the change and confirming the result.
For command-line Xcode tasks, xcodebuild or another tool may be part of the workflow if the course and host support it. Apple’s Xcode command-line tool reference documents command-line tools. A successful terminal build does not demonstrate that a student has opened the project in Xcode, operated its interface, or inspected a simulator. Treat those as separate acceptance steps.
Can SSH control Xcode directly?
SSH can run supported command-line tools on the Mac. It does not provide the Xcode window or simulator display. If the assignment requires visual inspection or interaction with Xcode, arrange approved graphical access and verify that the course permits it. Apple’s screen-sharing instructions cover a separate way to view and control a Mac screen.
[ SECTION_06 ] Use this checklist to choose the next step
Check each item before treating the remote setup as ready:
- [ ] The Windows Desktop app and its current feature support meet the official requirements.
- [ ] The Mac administrator has provided an authorized SSH host, username, and port.
- [ ] The remote account can access the intended course project.
- [ ] The private key stays on the student’s device and is not pasted into prompts or shared messages.
- [ ] Claude Code identifies the expected remote project folder.
- [ ] A harmless file listing or explanation confirms that commands are running on the Mac.
- [ ] The student has reviewed every proposed code change before accepting it.
- [ ] The required terminal check passes, or its failure has been reported accurately.
- [ ] Any requirement to operate Xcode or view a simulator has a separate graphical-access plan.
If the first seven checks pass and the course accepts terminal-based work, continue with the SSH workflow. If the project must be opened and inspected in Xcode, arrange graphical access before the deadline rather than assuming SSH will show the screen. If remote login is blocked by a school policy, request an approved alternative instead of bypassing it.
The remote Mac access options from NOVAKVM can help a student compare an approved remote environment with the computer already available. A remote Mac is not automatically the right fit: SSH access alone will not satisfy a visual Xcode requirement, and a student who needs a Mac running continuously for long-term work may prefer hardware they control directly. But relying only on a Windows computer can leave Mac-only tools unavailable, while a managed school computer may restrict installations and remote access. If the course requires macOS and no suitable Mac is available, renting a Mac from NOVAKVM can provide a separate environment to test against the assignment requirements. Review the Mac mini access option, confirm the connection method and graphical-access needs before choosing, and rent only if that setup matches the course.