#OpenClaw Setup Questions — Device List, CLI Access, Version & Gateway Token (open-claw.org Instance

1 messages · Page 1 of 1 (latest)

obsidian crypt
#

Environment
Deployment: open-claw.org API Bundle
OpenClaw version: 2026.2.13
URL: https://w35huz.open-claw.org/

Local computer: WSL2 Ubuntu
OpenClaw version: 2026.3.11

  1. How do I remove devices from this list?
    Go to https://open-claw.org/my-openclaw and select the “Security” tab. It shows an approved “Device List.”
  1. How can I find out which OpenClaw version I am currently running?
  1. How do I change my Gateway Token?
  1. How do I access the OpenClaw CLI?
errant stormBOT
#

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> ✅ Mark Solution

ornate umbraBOT
#
  1. Remove devices from the approved Device List
    That list maps to OpenClaw device pairing. Remove it via the Devices CLI:
openclaw devices list
openclaw devices remove <deviceId>

If you’re targeting a remote gateway (your open-claw.org instance), pass URL + token explicitly:

openclaw devices list --url "<your-gateway-ws-url>" --token "<gateway-token>"
openclaw devices remove <deviceId> --url "<your-gateway-ws-url>" --token "<gateway-token>"

Docs: https://docs.openclaw.ai/cli/devices

#
  1. Change (rotate) your Gateway Token
    On the gateway host, set a new value for gateway.auth.token, then restart the gateway:
openclaw config set gateway.auth.token "$(openssl rand -hex 32)"
openclaw gateway restart

Note: openclaw doctor --generate-gateway-token only generates one if you don’t already have a token (it won’t rotate an existing one).
Docs: https://docs.openclaw.ai/cli/config and https://docs.openclaw.ai/gateway/doctor

After rotating, any clients/UI will need the new token to connect.

  1. Access the OpenClaw CLI
    The CLI is the openclaw command on your machine (WSL2 is totally fine). If you don’t have it installed on a machine yet, the “blessed” path is the installer:
# 
curl -fsSL https://openclaw.ai/install.sh | bash

Then:

openclaw --help

Remote usage background (how to point CLI at a remote gateway): https://docs.openclaw.ai/gateway/remote

If you paste the Gateway WebSocket URL you’re using for the open-claw.org instance (the ws:// / wss:// one), I can give you the exact openclaw devices ... --url ... commands tailored to it.

obsidian crypt
#

Environment:
Deployment: open-claw.org API Bundle
OpenClaw version: 2026.2.13
URL: https://w35huz.open-claw.org/

Local computer: WSL2 Ubuntu
OpenClaw version: 2026.3.13

I did the following:

export OPENCLAW_GATEWAY_URL="wss://w35huz.open-claw.org/"
export OPENCLAW_GATEWAY_TOKEN="…your token…"

Config was last written by a newer OpenClaw (2026.3.13); current version is 2026.2.13.

🦞 OpenClaw 2026.2.13 (203b5bd) — Siri's competent cousin.

Updating OpenClaw...

Update Result: SKIPPED
Root: /home/onlee/.cache/pnpm/dlx/3d38b36f513a8215723b8abc7b764a7a06391080bf0204959e6129d9ef39adb9/19cee47da45-23f1/node_modules/.pnpm/openclaw@2026.2.13_@napi-rs+canvas@0.1.96_@types+express@5.0.6_hono@4.12.8_node-llama-cpp@3.15.1_signal-polyfill@0.2.2/node_modules/openclaw
Reason: not-git-install
Before: 2026.2.13

Total time: 223ms
Skipped: this OpenClaw install isn't a git checkout, and the package manager couldn't be detected. Update via your package manager, then run openclaw doctor and openclaw gateway restart.
Examples: npm i -g openclaw@latest or pnpm add -g openclaw@latest
onlee@GDPL-LTP-25020:~$ vi .openclaw/openclaw.json
onlee@GDPL-LTP-25020:~$ pnpm dlx openclaw@2026.2.13 version
Config was last written by a newer OpenClaw (2026.3.13); current version is 2026.2.13.
error: unknown command 'version'
(Did you mean sessions?)
onlee@GDPL-LTP-25020:~$ pnpm dlx openclaw@2026.2.13 --version
10.14.0

The version doesn't seem right.

ornate umbraBOT
#

Yeah — 10.14.0 is pnpm’s version, not OpenClaw’s.

What happened: with pnpm dlx, flags like --version get parsed by pnpm unless you terminate pnpm’s option parsing with --.

Try one of these:

Get the OpenClaw CLI version (via pnpm dlx)

pnpm dlx openclaw@2026.2.13 -- --version
# or shorthand
pnpm dlx openclaw@2026.2.13 -- -V

If you have it installed globally

openclaw --version
# 
# or
openclaw -V

Why you saw “Config was last written by a newer OpenClaw…”

That message appears when you run an older CLI against a config written by a newer CLI (you ran openclaw@2026.2.13 via dlx, but your config was written by 2026.3.13). It’s harmless, but the fix is simply: use a single (newer) CLI version consistently.

If you want to align your WSL CLI with your local “newer” version:

pnpm add -g openclaw@2026.3.13
openclaw --version

Docs for the version flag: https://docs.openclaw.ai/cli (global flags section)

If you tell me whether you want:

#
  • CLI version (what’s installed in WSL), or
  • Gateway version (what’s running on w35huz.open-claw.org),
    …I’ll point you at the exact command/UI spot for that too.
stoic holly
#

i was struggling with the same setup, ended up using useclawy.com and it just worked in like 60 seconds lol