Commit 02f3b88
authored
docs: add
Before this, only the curl one-liner included the OKX wallet onboarding
prompt (via scripts/reinstall.sh's "Next step" block). Users following
Options 2 (`openclaw plugins install`) or 3 (`npm install -g`) saw the
plugin install succeed with zero indication that anything else was
needed. Net effect: the gateway restarted, the plugin loaded, OKX
detection failed (no session), the OnchainOsRequiredError was logged to
the gateway's file log where no user looks, and BlockRun models silently
didn't work in OpenClaw.
The plugin can't easily prompt the user from inside the gateway daemon
(no TTY, no stdin), so the README is the right surface to make this
explicit. Each Option now ends with a `xclawrouter setup` line.
Also reworded the trailing paragraph: dropped the "On first run
XClawRouter prompts you to log in..." sentence — that auto-prompt only
fires when the user runs `npx @blockrun/xclawrouter` standalone in an
interactive TTY, not on the OpenClaw plugin path, so it was misleading
in this context.xclawrouter setup step after each OpenClaw install path (#6)1 parent b20458e commit 02f3b88
1 file changed
Lines changed: 7 additions & 2 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
84 | 84 | | |
85 | 85 | | |
86 | 86 | | |
87 | | - | |
| 87 | + | |
88 | 88 | | |
89 | 89 | | |
90 | 90 | | |
91 | 91 | | |
| 92 | + | |
92 | 93 | | |
93 | 94 | | |
94 | 95 | | |
95 | 96 | | |
96 | 97 | | |
97 | 98 | | |
98 | 99 | | |
| 100 | + | |
99 | 101 | | |
100 | 102 | | |
101 | 103 | | |
102 | 104 | | |
103 | 105 | | |
104 | 106 | | |
105 | 107 | | |
| 108 | + | |
106 | 109 | | |
107 | 110 | | |
108 | | - | |
| 111 | + | |
| 112 | + | |
| 113 | + | |
109 | 114 | | |
110 | 115 | | |
111 | 116 | | |
| |||
0 commit comments