v2026.4.14

Sync with upstream OpenClaw v2026.4.14

Changes

• Gateway entrypoint compatibility: Verify both dist/index.js (canonical) and dist/entry.js (legacy) in installer and updater, ensuring safe upgrades across versions
• Startup optimization: Add systemd drop-in for NODE_COMPILE_CACHE and OPENCLAW_NO_RESPAWN (upstream recommended for VM/ARM hosts). Uses bridge pattern — auto-removed when upstream takes over natively
• New model: Add gpt-5.4-pro forward-compat entry to config template
• Doctor docs: Correct --fix/--repair documentation (they are aliases), add all upstream flags (--force, --yes, --generate-gateway-token)
• Fix plugin deps install: Swap doctor --fix execution order — sudo first (installs deps into root-owned global npm prefix), then chown, then non-sudo (config migration). Previously the non-sudo run left partial npm state that blocked the subsequent sudo install
• Uninstall cleanup: Remove systemd drop-in on uninstall

Upstream highlights (v2026.4.14)

Quality/bugfix release — no new config options required:

• gpt-5.4-pro forward-compat support
• Gateway entrypoint unified to dist/index.js in doctor/update internals
• Ollama streaming usage fix (prevents premature compaction)
• Memory/Ollama embedding adapter restored
• TTS voice note persistence fix
• UI security: marked.js → markdown-it (ReDoS fix)
• Multiple Browser/SSRF fixes and security hardening

Known community issues (v2026.4.14)

• Active Memory may cause slowdowns on some setups (#66708) — workaround: disable plugin temporarily
• Telegram setMyCommands not registering at startup (#66682) — cosmetic, bot still functional
• Subagent completion may send duplicate messages (#66519) — UX issue, no data loss

Full upstream changelog: https://github.com/openclaw/openclaw/releases/tag/v2026.4.14