Step-by-Step Fix
1. Quit the App Completely
Do not just close the window. The OpenClaw desktop app often runs as a background process even when the window is closed. Quit it fully:
- macOS: Right-click the OpenClaw icon in the Dock, select Quit, or use Cmd+Q with the app in focus. Check the menu bar for the OpenClaw icon and quit from there if present.
- Windows: Right-click the OpenClaw icon in the system tray (bottom right), select Quit or Exit. Then open Task Manager (Ctrl+Shift+Esc) and verify no OpenClaw processes are running.
2. Check for App Updates
An outdated desktop app is a common cause of login failures, particularly after OpenClaw changes their authentication system.
- macOS: Relaunch the app and look for an update notification, or go to the app menu > Check for Updates
- Windows: Same — look for an update prompt on launch or a Check for Updates menu item
- Manual update: Download the latest version from openclaw.com/downloads, install it over the existing version
3. Clear the Local Credential Cache
If updating did not help, clear the app's stored credentials and session data:
macOS:
~/Library/Application Support/OpenClaw/ (delete contents)
~/Library/Caches/OpenClaw/ (delete contents)
Open Finder, press Cmd+Shift+G, enter the path, and delete the folder contents. Do not delete the folders themselves — just the files inside.
Windows:
%APPDATA%\OpenClaw\ (delete contents)
%LOCALAPPDATA%\OpenClaw\ (delete contents)
Press Win+R, type the path, press Enter, and delete the folder contents.
4. Relaunch and Attempt Login
After clearing the cache, relaunch the OpenClaw app. You should see a fresh login screen. Sign in with your credentials.
If the app uses OAuth (which opens your browser), watch for the browser to complete authentication and then redirect back to the app. If the redirect does not happen automatically, switch back to the desktop app — some versions detect the completed browser auth and update themselves.
5. Check the OAuth Redirect Setup
If login consistently opens the browser but never returns to the app:
-
Check that OpenClaw is set as the handler for
openclaw://URLs:- macOS: Open Terminal, run
open openclaw://test— if the app opens, the URL scheme is registered correctly - Windows: Run
start openclaw://testin Command Prompt
- macOS: Open Terminal, run
-
If the URL scheme is not registered, reinstall the app from openclaw.com — the installer registers the scheme automatically
-
As a fallback, look for a "Copy auth token" option in the browser after authentication and paste it manually if the app provides an input for this
6. Test on the Web Interface
While troubleshooting the desktop app, confirm that your account credentials are correct by signing in at app.openclaw.com in your browser. If web login works but desktop login fails, the issue is isolated to the desktop app (not your account), which makes the diagnosis easier to communicate to support.
7. Reinstall If All Else Fails
If clearing cache and updating did not resolve the issue:
- Uninstall OpenClaw from your system (macOS: drag to Trash + delete the Library folders above; Windows: Apps & Features > uninstall)
- Restart your computer
- Download the latest installer from openclaw.com
- Install fresh
- Sign in
Your workflows and configurations are stored server-side and will be fully accessible after reinstalling.
Why This Happens
The OpenClaw desktop app is built on Electron (a framework for cross-platform desktop apps using web technologies). Electron apps store session tokens and OAuth credentials in local files on your computer. When these files become corrupted, outdated, or reference an invalidated session, the login process fails silently or produces a blank screen. This is more common after system updates (macOS major versions, Windows updates) that can corrupt app data directories, after interrupted app updates, or after Electron's internal storage engine encounters a write error.
Common Mistakes to Avoid
- Only closing the window without quitting: The background process retains the stale session state, so relaunching just reopens the same broken state.
- Clearing browser cache instead of app cache: Browser cache settings do not affect the desktop app's local storage. The app's data lives in the Application Support or AppData folder, not the browser.
- Not checking for updates first: Installing a fresh version of the app often resolves login issues more quickly than manual cache-clearing steps.
- Continuing to use an old app version: OpenClaw's authentication system may change in ways that break older app versions. Staying current prevents most login regressions.
FAQ
Q: Does clearing the desktop app cache delete my workflows and automation data?
No. OpenClaw stores your workflows, agent configurations, run history, and account data on their servers, not locally on your computer. Clearing the local app cache only removes session tokens, cached preferences, and temporary UI state. Your data is fully preserved and immediately accessible after you sign back in following a cache clear.
Q: The OpenClaw app opens but shows a perpetual loading spinner. Is this a cache issue?
A perpetual loading spinner on launch is almost always either a cache corruption issue or a version mismatch between the app and the server. Clear the app cache first (see steps above for your OS). If the spinner persists, check whether OpenClaw has an active incident at their status page — server-side issues can cause the initial dashboard load to hang indefinitely. If neither applies, reinstall the app.
Q: OpenClaw desktop app login works sometimes but fails randomly. What causes intermittent failures?
Intermittent login failures on the desktop app are often caused by unreliable network conditions during the OAuth callback: the browser completes authentication, attempts to redirect back to the app, and the redirect is dropped by a brief network interruption. Using a stable Wi-Fi connection rather than a mobile hotspot during login, and ensuring the app is fully quit and relaunched before each login attempt, reduces intermittent failures. If the issue persists on stable connections, report it to support with timestamps and your OS version.
Q: Can I run OpenClaw desktop app alongside the web version simultaneously?
Yes, but they maintain separate sessions. Changes made in the desktop app (running an agent, updating a workflow) are reflected immediately in the web version since both connect to the same server-side data. However, signing out in one does not sign out the other — the desktop app and web version each manage their own session token independently.
Q: Which desktop app version should I be running?
Always run the latest version available from openclaw.com/downloads. OpenClaw does not maintain multiple supported version branches — older versions may stop working entirely when the server API is updated. The app checks for updates on launch and displays a notification if a newer version is available. Install updates promptly to avoid login and feature failures caused by API version mismatches.
Related Issues
- OpenClaw login/auth issues – session expired
- OpenClaw login not working on mobile (iOS/Android)
- OpenClaw login & API key issues
- OpenClaw temporary restrictions – suspicious activity flags
Additional FAQ
Q: What is the fastest way to diagnose a login problem? The fastest diagnostic is to open an incognito or private browser window and attempt to sign in there. Incognito windows run without extensions and use fresh cookies, which isolates the two most common causes: a browser extension interfering with authentication, or corrupted session cookies. If login works in incognito, the issue is your main browser profile. If it still fails, the problem is your network, your account, or a platform-side incident.
Related Articles
- OpenClaw login / API key fix
- OpenClaw rate limits affecting runs
- OpenClaw agent not starting
- OpenClaw tool calls failing