Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Upgrade OpenClaw to 2026.3.23 and Node 24
abc@e4210d2c6416:~$ ollama launch openclaw --model kimi-k2.5:cloud
Launching OpenClaw with kimi-k2.5:cloud...
Security
OpenClaw can read files and run actions when tools are enabled.
A bad prompt can trick it into doing unsafe things.
Learn more: https://docs.openclaw.ai/gateway/security
Updating OpenClaw...
│
◇ ✓ Updating via package manager (104.06s)
│
◇ ✓ Running doctor checks (11.3s)
Update Result: OK
Root: /usr/local/lib/node_modules/openclaw
Before: 2026.3.23-2
After: 2026.3.23-2
Total time: 116.45s
Updating plugins...
No plugin updates needed.
Restarting service...
Gateway service disabled.
Start with: openclaw gateway install
Start with: openclaw gateway
Start with: systemctl --user start openclaw-gateway.service
I've seen things you wouldn't believe. Anyway, I'm updated.
Setting up OpenClaw with Ollama...
Model: kimi-k2.5:cloud
🦞 OpenClaw 2026.3.23-2 (7ffe7e4)
Claws out, commit in—let's ship something mildly responsible.
Default Ollama model: kimi-k2.5:cloud
Config overwrite: /config/.openclaw/openclaw.json (sha256 5e76aea33f852a9dc106820308127e07a22ab77ded5e7ac7fd233b23bd2334d5 -> 40ecbee3bfde2c29251b3b9fe7252cf7befd3c472001ca3c22aa8c7aae0e4b12, backup=/config/.openclaw/openclaw.json.bak)
Config write anomaly: /config/.openclaw/openclaw.json (missing-meta-before-write)
Updated ~/.openclaw/openclaw.json
Workspace OK: ~/.openclaw/workspace
Sessions OK: ~/.openclaw/agents/main/sessions
Gateway did not become reachable at ws://127.0.0.1:18789.
Last probe: gateway closed (1006 abnormal closure (no close frame)): no close reason
Non-interactive local setup only waits for an already-running gateway unless you pass --install-daemon.
Fix: start
openclaw gateway run, re-run with--install-daemon, or use--skip-health.Error: openclaw onboarding failed: exit status 1
Try running: openclaw onboard
Secured.OpenClaw.WebTop-small.mp4