Start with a task. Use the architecture only when you need it.
The fastest way to understand LocalCommander is to connect one PC and run one real workflow. The technical details below explain what happens after that.
Get from zero to a working task.
Open the control center and sign in.
Download the installer, run it and pair the PC with a one-time code.
Use the web version of ChatGPT. Until the public listing is available, connect the remote MCP endpoint in Developer Mode.
Ask: “List my paired PCs and tell me which one is online.”
What it can do
The live Windows app can combine several kinds of work inside one task:
Find, inspect, rename, move and return files from the paired computer.
Navigate pages, fill forms, work with tables, uploads and downloads.
Use native controls and, when necessary, visual targeting and input.
Run approved commands, inspect processes and keep longer jobs alive.
How it works
ChatGPT | v LocalCommander cloud | v Your paired Windows PC | +-- Files +-- Browser +-- Windows apps +-- Terminal
ChatGPT talks to the LocalCommander cloud service. Your Windows app keeps an authenticated outbound connection to that service. Approved tasks are routed to the paired PC; the result is returned to the conversation.
Your PC does not need a public inbound port.
Permissions and approvals
LocalCommander exposes different tool levels so normal tasks do not automatically get administrative access.
Normal file, browser, UI and desktop work.
Commands, process sessions and advanced developer or machine operations.
Services, registry, scheduled tasks and filesystem permissions.
Power and Admin access require explicit authorization. Internal maintenance and unsafe-to-publish tools remain private.
Troubleshooting
Confirm Developer Mode is enabled and the exact /mcp endpoint was added.
Open the LocalCommander dashboard and confirm the Windows machine shows Online.
Open the Windows companion and check that it is still running and connected.
Approve the requested action in the ChatGPT flow if you trust it.
Future apps
Browser Operator, Files & Office, Sales Operator and Agent Runtime are separate product tracks. They are not required to use LocalCommander Windows and are not presented as released until their own product surfaces are ready.
See the app roadmap →