#dependency-error
Sorted by views, then solution_desc, solution, and root_cause length (desc).
2534 issues
After upgrading to OpenClaw 2026.3.13 on Windows, the ACP runtime backend is unavailable. This appears to be a recurrence of #43997, but with two compounding issues specific to Windows.
`task-manager` workers can resolve `SKILL.md` from the bundled OpenClaw install path instead of the current workspace path, which causes startup to fail with `ENOENT`.
The `openclaw gateway restart` command sends SIGTERM to the gateway process but does not verify that the gateway successfully restarts. This can leave the gateway down for extended periods with no error indication or automatic recovery.
Request to add **ACP (Agent Client Protocol) runtime support** for the Feishu (Lark) channel, enabling automatic ACP session routing for external coding harnesses like OpenCode, Claude Code, Codex, etc.
The built-in auto-update consistently kills the gateway on macOS with no recovery, leaving the service unloaded indefinitely. The root cause is that `resolveCommandStdio` forces piped stdout/stderr for the update subprocess, creating a fatal dependency on the gateway parent process — which is then killed by `launchctl bootout` during the restart step. This is the underlying mechanism behind several related reports (#54861, #57379, #58041, #40811, #48992) that describe symptoms (service unloaded, multi-hour outages, KeepAlive not respected) without pinpointing why the restart handoff never completes.
OpenClaw 2026.3.11 on Ubuntu VPS. gog CLI works and Google OAuth is successful. openclaw skills check shows gog as ready. But when running in the browser: /skill gog gmail labels list the UI returns: No session found: gog Gateway logs show: sessions.resolve errorMessage=No session found: gog The gog CLI works directly from the VPS.
After updating OpenClaw on Windows to the 2026-03-31 build, the Telegram plugin regressed and no longer starts. This setup was working before the update. After the update, Telegram fails to load at startup with: ```text telegram failed to load from C:\Users\Illidan\AppData\Roaming\npm\node_modules\openclaw\dist\extensions\telegram\index.js: Error: Cannot find module 'grammy' Require stack: - C:\Users\Illidan\AppData\Roaming\npm\node_modules\openclaw\dist\sticker-cache-1Tf7t-45.js
Description: After updating to 2026.3.28 (f9b1079), agents cannot execute any commands. The exec tool fails validation with: Validation failed for tool "exec": command: must have required property 'command' Received arguments: {}Environment: • OpenClaw version: 2026.3.28 (f9b1079) • OS: macOS 15.3.2 (Darwin 25.3.0 arm64) • Install method: npm global • Model: kimi-coding/k2p5 Config (tools section): "tools": { "profile": "full", "allow": ["*"], "exec": { "host": "gateway", "security": "full", "ask": "off" } }Tried: • ✅ Latest version 2026.3.28 • ✅ Downgrade to 2026.2.21 • ✅ Config fix (exec settings with ask: "off") • ✅ Multiple gateway restarts • ✅ All "workarounds" from #39691 Result: Still broken. The agent generates commands but they never execute. Impact: Completely blocks autonomous agent functionality.