OCC Desktop OCC Desktop

Support for OCC Desktop

If you need help getting OCC Desktop connected, paired, or working cleanly with your OpenClaw setup, start here.

This page covers the most common setup problems, the user manual, and how to contact support when you need a human.

Download Manual Read Setup FAQ

The support chat opens as a corner panel and leaves the rest of this page intact.

Contact Support

For support, email:

support@occdesktop.com

When possible, include:

  • your Linux distro/version
  • your OCC Desktop version
  • the exact step where setup failed
  • the exact error message you saw
  • whether the problem is token, pairing, or general connectivity

User Manual

The OCC Desktop manual covers installation, onboarding, pairing, support tools, and uninstall instructions.

Download OCC Desktop Manual (PDF)

Before You Email Support

  • confirm OpenClaw is installed and running
  • confirm your gateway token is correct
  • confirm OCC Desktop can reach your gateway host and port
  • check whether a pairing request is waiting for approval

Setup & Troubleshooting FAQ

How do I get my OpenClaw gateway token?
On the machine where OpenClaw is installed, run:
python3 -c 'import json, pathlib; print(json.load(open(pathlib.Path.home()/".openclaw/openclaw.json"))["gateway"]["auth"]["token"])'
Copy the token value shown and paste it into OCC Desktop during setup.
That command says the file was not found. What now?
That usually means OpenClaw was installed/configured in a nonstandard way, or the current user account is not the one that owns the OpenClaw config.
Check for the actual config file location, then look for the token under gateway.auth.token. If OpenClaw is not installed cleanly, fix that first before troubleshooting OCC Desktop.
The token test works, but OCC Desktop does not appear in pairing/devices.
If OCC Desktop is not showing up as a pending device, the problem is usually not the token itself. It is usually one of these:
  • OpenClaw is installed or configured in a nonstandard way
  • the gateway route/host/port is wrong
  • the pairing flow is not actually reaching the expected gateway
In plain English: token success alone does not prove pairing is working.
How do I pair OCC Desktop with OpenClaw?
After entering a valid token and connecting successfully, OCC Desktop may show a pairing screen if approval is required.
  1. Open the OpenClaw WebUI
  2. Go to the nodes/devices approval area
  3. Approve the pending OCC Desktop device
  4. Return to OCC Desktop and reconnect
Why is pairing not appearing at all?
If pairing never appears, verify that:
  • OpenClaw is actually running
  • the host/port in OCC Desktop point to the real gateway
  • the token belongs to that same gateway
  • OpenClaw was installed with the normal supported method instead of an improvised/manual layout
How do I run the OCC Desktop installer on Linux?
After downloading the .run installer, make it executable first:
chmod +x OCC-Desktop-Installer-v0.3.50.run
Then run it:
./OCC-Desktop-Installer-v0.3.50.run
If you skip the chmod +x step, Linux may refuse to launch the installer.
What is the best way to install OpenClaw on Linux?
Install the normal prerequisites first, then install OpenClaw cleanly through the standard Node/npm route.
sudo pacman -Syu
sudo pacman -S nodejs npm git
sudo npm install -g openclaw
After that, verify the install with:
openclaw --version
openclaw status
openclaw qr --json