LocalCommander for Windows: setup and technical details.
Windows is the main product. The macOS beta supports 14 scoped tools; Android remains a prototype. Read setup, permissions and platform limitations.
START HERE
Installing LocalCommander for the first time?
Open the full guide: 10 steps and 9 screenshots — from creating your account and installing Windows to connecting ChatGPT.
From a new account to the first real task.
Open the LocalCommander control center.
Windows supports full desktop work, macOS beta supports scoped file/diagnostic tools, and Android is an experimental mobile prototype.
Pair supported devices with browser approval and device-scoped credentials. The Mac beta still requires real-device E2E verification.
The dashboard should show the platform, agent version and live device state.
Install LocalCommander from ChatGPT Plugins and authorize the same LocalCommander account.
Ask LocalCommander to list connected devices before trying a write action.
How a tool reaches the right device.
ChatGPT / MCP client
|
v
LocalCommander MCP gateway
auth · scopes · limits · platform routing
|
+-----+----------------+----------------+
| | |
v v v
Windows agent macOS beta Android prototype
files / apps / scoped files mobile apps / UI
browser / OS diagnostics approved gesturesChatGPT talks to the public LocalCommander MCP gateway. The gateway authenticates the user, enforces scopes and plan limits, inspects device ownership and live capabilities, and routes the request to a compatible device agent. The result returns through the gateway to the conversation.
Windows, macOS beta and Android use outbound connections; no public inbound device port is required.
Windows agent
The Windows runtime is the broad desktop operator. It handles local files, structured documents, browser automation, native Windows UI, terminal/process work and selected system functions.
Local and structured-file workflows, transforms, hashes and exports.
DOM/CDP-first navigation, forms, tables, uploads, downloads and verification.
Native controls first, then visual/input fallbacks where necessary.
Approved commands, process inspection and longer-running sessions.
Selected networking, clipboard, service and administrative tools according to scope.
macOS native beta
macOS 13+ on Apple Silicon and Intel. The 0.1.0 beta supports 14 scoped file and diagnostics tools, account approval and outbound relay. It is not feature-equivalent to Windows, is ad-hoc signed and not Apple-notarized. A real Mac pairing and tool-execution test is still outstanding.
Android prototype
The Android runtime is an experimental prototype installed as an APK. It exposes exactly 12 Android-specific public tools and advertises live capabilities based on user-granted permissions.
Device model, Android version, agent version, permission state and live capabilities.
List launchable apps, open an app and open supported URIs.
Read the Accessibility tree and click visible text.
Tap, swipe, type text and press supported navigation keys.
Capture the visible screen where Android permits it.
Read notifications only after separate notification-access approval.
- Root is not required for the production Android flow.
- ADB and a computer are not required to install or connect the Android agent.
- Accessibility must be enabled by the user before screen automation works.
- Notification access is a separate optional permission.
- Secure windows may block screenshots.
- PIN and biometric gates remain system-controlled.
- Other apps' private sandbox data is not exposed.
Authorization happens before routing.
The model does not decide access. The gateway enforces OAuth scopes, account ownership, device ownership, plan limits and platform capabilities. Android permissions are also enforced locally by the operating system.
OAuth 2.1 + PKCE · authorization code + PKCE · refresh-token rotation.
Only devices connected to the authorized LocalCommander account can be targeted.
A tool fails closed when no compatible connected device advertises the required capability.
Windows and Android still enforce their own user/system permission models.
Current ChatGPT connection status.
LocalCommander is available in ChatGPT Plugins. Search for the plugin, install it, and authorize your LocalCommander account to reach connected devices.
Open ChatGPT Plugins ↗Open the ChatGPT Plugins directory and search for LocalCommander.
Choose LocalCommander by Solidcodeapps.pl and select Install plugin.
Sign in to the same LocalCommander account that you used to connect your PC.
Describe your task and the files or programs to use. If several PCs are connected, name the one you want to work on.
Troubleshooting by platform.
Open the relevant Windows or Android agent and confirm its outbound relay is connected.
Open Android Accessibility settings and enable LocalCommander device control.
Confirm notification access is enabled separately for LocalCommander.
The current screen may be secure or otherwise protected by Android.
Use Open browser again in the Windows app; the one-time pairing code is Windows fallback only.
Search ChatGPT Plugins for LocalCommander, confirm installation, and complete account authorization.
Specify the device explicitly or set the preferred device in the LocalCommander control center.