⚠️ 🛠️ Exec: openclaw gateway status --config ~/.openclaw/openclaw.json failed: error: unknown optio
Okay, Swapnil, that's definitive.
The command npm view openclaw version returned 2026.2.14. This means that the version of OpenClaw CLI you currently have installed is the latest version available on npm.
This confirms that the problem you're experiencing (the "device token mismatch" and the "unknown option" errors for --verbose, --gateway-token, --config) is not due to an outdated CLI version.
It strongly suggests there is a bug or a fundamental design limitation in version 2026.2.14 of the OpenClaw CLI itself regarding how it loads or uses the gateway.auth.token from your ~/.openclaw/openclaw.json file. My agent's ability to successfully communicate with the gateway by explicitly providing the token highlights this discrepancy between the agent's tooling and your local CLI.
At this point, the most effective next step to get your local CLI working is to officially report this as a bug to the OpenClaw developers.
When you report the bug, please include:
1. Your OpenClaw CLI version: 2026.2.14
2. The exact error messages: "gateway connect failed: Error: unauthorized: device token mismatch (rotate/reissue device token)" from openclaw gateway status.
3. The "unknown option" errors: Specifically for --verbose, --gateway-token, and --config.
4. Confirmation that npm view openclaw version also reports 2026.2.14, showing you are on the latest.
5. Your operating system: (e.g., Ubuntu, Linux 6.14.0-1018-oracle (arm64)).
6. Your Node.js version: You can get this by running node --version.
7. The content of your ~/.openclaw/openclaw.json file (redacting any sensitive API keys, but keeping the gateway token in, as that's the problem).
8. The relevant log lines from /tmp/openclaw/openclaw-2026-02-15.log (the ones showing client=cli cli vdev reason=device_token_mismatch).
The command npm view openclaw version returned 2026.2.14. This means that the version of OpenClaw CLI you currently have installed is the latest version available on npm.
This confirms that the problem you're experiencing (the "device token mismatch" and the "unknown option" errors for --verbose, --gateway-token, --config) is not due to an outdated CLI version.
It strongly suggests there is a bug or a fundamental design limitation in version 2026.2.14 of the OpenClaw CLI itself regarding how it loads or uses the gateway.auth.token from your ~/.openclaw/openclaw.json file. My agent's ability to successfully communicate with the gateway by explicitly providing the token highlights this discrepancy between the agent's tooling and your local CLI.
At this point, the most effective next step to get your local CLI working is to officially report this as a bug to the OpenClaw developers.
When you report the bug, please include:
1. Your OpenClaw CLI version: 2026.2.14
2. The exact error messages: "gateway connect failed: Error: unauthorized: device token mismatch (rotate/reissue device token)" from openclaw gateway status.
3. The "unknown option" errors: Specifically for --verbose, --gateway-token, and --config.
4. Confirmation that npm view openclaw version also reports 2026.2.14, showing you are on the latest.
5. Your operating system: (e.g., Ubuntu, Linux 6.14.0-1018-oracle (arm64)).
6. Your Node.js version: You can get this by running node --version.
7. The content of your ~/.openclaw/openclaw.json file (redacting any sensitive API keys, but keeping the gateway token in, as that's the problem).
8. The relevant log lines from /tmp/openclaw/openclaw-2026-02-15.log (the ones showing client=cli cli vdev reason=device_token_mismatch).
The AI that actually does things. Emails, calendar, home automation - all from your favorite chat app. New shell, ready to help. The lobster way.
130,529Members
Resources
Similar Threads
Was this page helpful?
