LocalCommander shows Offline? Windows connection troubleshooting step by step
If your PC shows Offline, check the execution device first before changing ChatGPT settings.
An Offline status usually means that the LocalCommander service cannot currently route a task to that device. The fastest way to diagnose it is to work from the Windows agent outward rather than changing several unrelated settings at once.
Keep Windows and the Android prototype separate during diagnosis. If your goal is to use the main product, confirm the Windows device first.
1. Check whether the Windows app is running
Open LocalCommander on the PC and confirm that the app starts normally. If the app is not running, the cloud service cannot receive a live connection from that machine.
Avoid restarting the whole computer as the first response. Check the app state and any visible error first.
2. Verify internet access and time
Confirm that the PC can reach normal HTTPS websites and that system time is correct. Authentication and secure connections can fail when the local clock is badly wrong.
VPNs, corporate firewalls or endpoint security can also affect outbound connections.
3. Check the device in the control center
Refresh the LocalCommander dashboard and look for the device name, status and last-seen time. Make sure you are signed in to the account that originally paired the machine.
A revoked device should be paired again rather than treated as an ordinary Offline device.
4. Reopen the pairing flow if needed
If the local app no longer has a valid pairing, use the normal browser approval flow again. Do not create multiple random device records unless the previous pairing is genuinely invalid.
After approval, wait for the device to report Online and verify the state in the dashboard.
5. Separate ChatGPT authorization from device connectivity
A Windows device can be Online even if the ChatGPT plugin is not authorized, and ChatGPT can be authorized even if a PC is Offline. Treat those as two different layers.
First confirm the device. Then confirm LocalCommander authorization inside ChatGPT.
6. Run a read-only check
Once the device is Online, send a simple task that produces a result without changing files. This confirms the route end to end.
If status is Online but every tool call fails, capture the exact error and the tool or task that triggered it.
Show my connected LocalCommander devices and identify the Windows PC that is currently Online. Then list the five newest files in Downloads without changing anything.
7. When to collect diagnostics
If the issue returns, record app version, Windows version, approximate failure time, network context and any visible error. That is more useful than repeatedly reinstalling without evidence.
Use the support channel when the service or account layer appears healthy but the agent cannot establish a stable connection.
Good to know: Do not expose passwords, tokens or other secrets in support screenshots or diagnostic messages.
Turn the guide into a real task.
Connect your Windows PC, choose a low-risk task and verify the result. Start on the Free plan.