yunxiafei/openclaw-mission-control
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: fix gateway token description in openclaw_gateway_ws.md to match actual behavior

Browse Source 
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
Hugh Brown
2026-03-04 01:41:25 -07:00
committed by Abhimanyu Saharan
parent 528a2483b7
commit ee825fb2d5
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
docs/openclaw_gateway_ws.md
View File

@@ -25,6 +25,6 @@ When enabled, Mission Control skips TLS certificate verification for that gatewa
When configuring a gateway, you can specify:
- **Gateway URL**: The WebSocket endpoint (e.g., `wss://localhost:18789` or `ws://gateway:18789`)
- **Gateway Token**: Optional authentication token. For security, tokens are **never returned in API responses**. The API indicates only whether a token is configured (`has_token: true/false`). Store tokens securely at creation time; they cannot be retrieved later.
- **Gateway Token**: Optional authentication token. Tokens are currently returned in API responses; a future release will redact them from read endpoints. Treat gateway API responses as sensitive and store tokens securely.
- **Workspace Root**: The root directory for gateway files (e.g., `~/.openclaw`)
- **Allow self-signed TLS certificates**: Toggle TLS certificate verification off for this gateway's `wss://` connections (default: disabled)