@futurx/openclaw-operator-ui 0.1.1 → 0.1.3

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -12,7 +12,7 @@ A standalone plugin that provides a web-based management interface for [OpenClaw
12
12
  - **Session Management** — View, reset and delete conversation sessions
13
13
  - **Cron Jobs** — Monitor and control scheduled tasks
14
14
  - **System Settings** — Edit `openclaw.json` configuration, view system health and available models
15
- - **Password Authentication** — Secured via Gateway password
15
+ - **Token / Password Authentication** — Supports both Gateway token and password auth modes
16
16
 
17
17
  ## Installation
18
18
 
@@ -44,7 +44,19 @@ http://localhost:18789/operator
44
44
 
45
45
  - OpenClaw >= 2026.1.26
46
46
  - Node.js >= 22
47
- - Gateway must have password authentication configured in `~/.openclaw/openclaw.json`:
47
+ - Gateway must have authentication configured in `~/.openclaw/openclaw.json` — either token or password mode:
48
+
49
+ ```json
50
+ {
51
+ "gateway": {
52
+ "auth": {
53
+ "token": "your-token-here"
54
+ }
55
+ }
56
+ }
57
+ ```
58
+
59
+ or
48
60
 
49
61
  ```json
50
62
  {
@@ -56,9 +68,11 @@ http://localhost:18789/operator
56
68
  }
57
69
  ```
58
70
 
71
+ > If no auth is configured, the Gateway auto-generates a token on first startup and persists it to `openclaw.json`. You can find it under `gateway.auth.token`.
72
+
59
73
  ### Client ID
60
74
 
61
- This plugin connects to the Gateway using `openclaw-control-ui` as its client ID for maximum compatibility with any OpenClaw instance. A dedicated `openclaw-operator-ui` ID has been proposed upstream ([PR #29359](https://github.com/openclaw/openclaw/pull/29359)) and will be adopted in a future release once merged.
75
+ This plugin connects to the Gateway using `webchat-ui` as its client ID for maximum compatibility it works on any OpenClaw instance without requiring device identity or secure context. A dedicated `openclaw-operator-ui` ID has been proposed upstream ([PR #29359](https://github.com/openclaw/openclaw/pull/29359)) and will be adopted in a future release once merged.
62
76
 
63
77
  ## Development
64
78