openclaw - ✅(Solved) Fix Bug: v2026.4.25 still triggers WhatsApp runtime deps install via persisted auth state, causing libsignal-node SSH failure on startup [1 pull requests, 2 comments, 2 participants]

openclaw2026-04-27 13:47:07

ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

GitHub issue URL

Helpful · Quick feedback

GitHub stats

openclaw/openclaw#72836•Fetched 2026-04-28 06:31:43

View on GitHub

Comments

Participants

Timeline

Reactions

Author

xiao398008

Participants

steipete

xiao398008

Timeline (top)

commented ×2closed ×1cross-referenced ×1

After upgrading to OpenClaw 2026.4.25, Gateway startup still triggers WhatsApp runtime dependency installation even though WhatsApp is not explicitly enabled in config.

This leads to npm trying to resolve Baileys -> libsignal-node from GitHub over SSH, which fails on hosts without a GitHub SSH key:

[email protected]: Permission denied (publickey).
error code 128

The Gateway now appears to recover faster than before, so the failure is less catastrophic than earlier versions, but the incorrect startup/install path is still present.

Error Message

error code 128 error code 128 error code 128

Root Cause

After upgrading to OpenClaw 2026.4.25, Gateway startup still triggers WhatsApp runtime dependency installation even though WhatsApp is not explicitly enabled in config.

This leads to npm trying to resolve Baileys -> libsignal-node from GitHub over SSH, which fails on hosts without a GitHub SSH key:

[email protected]: Permission denied (publickey).
error code 128

The Gateway now appears to recover faster than before, so the failure is less catastrophic than earlier versions, but the incorrect startup/install path is still present.

Fix Action

Fix / Workaround

After upgrading to 2026.4.25, the local hotfix was overwritten and channel-catalog.json again contains the WhatsApp entry with persisted auth state probing:

Install/upgrade to 2026.4.25
Have persisted WhatsApp auth state present on disk
Do not explicitly enable WhatsApp in config
Restart Gateway
Observe runtime deps install attempt including Baileys/libsignal and SSH failure

PR fix notes

PR #72844: fix(channels): ignore persisted auth for auto-enable

Repository: openclaw/openclaw
Author: haishmg
State: closed | merged: False
Link: https://github.com/openclaw/openclaw/pull/72844

Description (problem / solution / changelog)

Summary

stop treating persisted channel auth state as configured channel state
exclude persisted-auth-only channels from plugin auto-enable candidate detection
document that persisted auth probes are for setup/status-style reporting, not runtime activation

Fixes #72836.

Verification

CI=true OPENCLAW_LOCAL_CHECK=0 npm exec [email protected] -- test src/config/channel-configured.test.ts src/config/plugin-auto-enable.core.test.ts src/channels/config-presence.test.ts src/plugins/channel-plugin-ids.test.ts
CI=true OPENCLAW_LOCAL_CHECK=0 npm exec [email protected] -- run check

Note: an initial pre-install test:changed/check attempt failed because the workspace was missing installed deps such as @sinclair/typebox; after npm exec [email protected] -- install, the focused tests and check passed.

Changed files

docs/plugins/manifest.md (modified, +4/-2)
src/config/channel-configured.test.ts (modified, +2/-12)
src/config/channel-configured.ts (modified, +0/-5)
src/config/plugin-auto-enable.core.test.ts (modified, +17/-0)
src/config/plugin-auto-enable.shared.ts (modified, +2/-2)

Code Example

git --no-replace-objects ls-remote ssh://git@github.com/whiskeysockets/libsignal-node.git
git@github.com: Permission denied (publickey).
error code 128

---

{
  "name": "@openclaw/whatsapp",
  "openclaw": {
    "channel": {
      "id": "whatsapp",
      "persistedAuthState": {
        "specifier": "./auth-presence",
        "exportName": "hasAnyWhatsAppAuth"
      }
    }
  }
}

---

@whiskeysockets/baileys@7.0.0-rc.9
libsignal@git+https://github.com/whiskeysockets/libsignal-node.git
git --no-replace-objects ls-remote ssh://git@github.com/whiskeysockets/libsignal-node.git
git@github.com: Permission denied (publickey).
error code 128

RAW_BUFFERClick to expand / collapse

Summary

After upgrading to OpenClaw 2026.4.25, Gateway startup still triggers WhatsApp runtime dependency installation even though WhatsApp is not explicitly enabled in config.

This leads to npm trying to resolve Baileys -> libsignal-node from GitHub over SSH, which fails on hosts without a GitHub SSH key:

[email protected]: Permission denied (publickey).
error code 128

The Gateway now appears to recover faster than before, so the failure is less catastrophic than earlier versions, but the incorrect startup/install path is still present.

Environment

OpenClaw version: 2026.4.25
Host: Linux
Install method: global npm install
Runtime deps path: /root/.openclaw/plugin-runtime-deps/openclaw-2026.4.25-4eca5026e977

Expected behavior

If WhatsApp is not explicitly enabled in config, Gateway startup should not trigger WhatsApp runtime dependency installation based only on persisted auth state.

Actual behavior

During Gateway startup, runtime deps resolution still includes WhatsApp-related packages:

@whiskeysockets/[email protected]
libsignal@git+https://github.com/whiskeysockets/libsignal-node.git

npm then attempts:

git --no-replace-objects ls-remote ssh://[email protected]/whiskeysockets/libsignal-node.git
[email protected]: Permission denied (publickey).
error code 128

Evidence

channel catalog restored after upgrade

After upgrading to 2026.4.25, the local hotfix was overwritten and channel-catalog.json again contains the WhatsApp entry with persisted auth state probing:

{
  "name": "@openclaw/whatsapp",
  "openclaw": {
    "channel": {
      "id": "whatsapp",
      "persistedAuthState": {
        "specifier": "./auth-presence",
        "exportName": "hasAnyWhatsAppAuth"
      }
    }
  }
}

npm debug log excerpts

@whiskeysockets/[email protected]
libsignal@git+https://github.com/whiskeysockets/libsignal-node.git
git --no-replace-objects ls-remote ssh://[email protected]/whiskeysockets/libsignal-node.git
[email protected]: Permission denied (publickey).
error code 128

Notes

This seems related to the previously known behavior where persisted auth state can incorrectly activate WhatsApp startup/install paths even without explicit config enablement.

In 2026.4.25, the Gateway eventually comes up, so startup impact is reduced, but the incorrect dependency resolution path still happens.

Repro outline

Install/upgrade to 2026.4.25
Have persisted WhatsApp auth state present on disk
Do not explicitly enable WhatsApp in config
Restart Gateway
Observe runtime deps install attempt including Baileys/libsignal and SSH failure

Request

Please confirm whether the persisted-auth-state startup gating fix is expected to be present in 2026.4.25, and if not, whether this is a regression or incomplete rollout.

extent analysis

TL;DR

The issue can be worked around by removing the persisted WhatsApp auth state or explicitly disabling WhatsApp in the config to prevent unnecessary runtime dependency installation.

Guidance

Verify that WhatsApp is not explicitly enabled in the config and that there is no persisted auth state for WhatsApp.
Check the channel-catalog.json file for any WhatsApp entries and remove them if present.
Consider adding a config option to explicitly disable WhatsApp if it's not intended to be used.
Investigate the previously known behavior where persisted auth state can incorrectly activate WhatsApp startup/install paths and determine if it's related to this issue.

Example

No code snippet is provided as the issue is related to configuration and dependency installation.

Notes

The issue seems to be related to the persisted auth state and the Gateway's behavior of installing runtime dependencies even when WhatsApp is not explicitly enabled. The fact that the Gateway recovers faster than before suggests that there might be some improvements in the new version, but the underlying issue remains.

Recommendation

Apply workaround: Remove the persisted WhatsApp auth state or explicitly disable WhatsApp in the config to prevent unnecessary runtime dependency installation. This is because the issue seems to be related to the persisted auth state and the Gateway's behavior, and removing or disabling WhatsApp should prevent the incorrect dependency resolution path.

Vote matrix · Quick signals

Works

Did the solution work? Tap to confirm.

Easy Fix

Was it a quick fix?

Time Saver

Did it save you time?

Blocking

Was it severely blocking?

Common Issue

Are others likely hitting this too?

Flaky / Intermittent

Is it intermittent?

Verified / Reproducible

Can you reproduce it reliably?

FAQ

Expected behavior

If WhatsApp is not explicitly enabled in config, Gateway startup should not trigger WhatsApp runtime dependency installation based only on persisted auth state.

#installation #index setup #retrieval issue #search optimization #API routing

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

openclaw - ✅(Solved) Fix Bug: v2026.4.25 still triggers WhatsApp runtime deps install via persisted auth state, causing libsignal-node SSH failure on startup [1 pull requests, 2 comments, 2 participants]

Recommended Tools

GitHub issue graph ai analysis

Error Message

Root Cause

Fix Action

Fix / Workaround

PR fix notes

PR #72844: fix(channels): ignore persisted auth for auto-enable

Description (problem / solution / changelog)

Summary

Verification

Changed files

Code Example

Summary

Environment

Expected behavior

Actual behavior

Evidence

channel catalog restored after upgrade

npm debug log excerpts

Notes

Repro outline

Request

extent analysis

TL;DR

Guidance

Example

Notes

Recommendation

FAQ

Expected behavior

Still need to ship something?

RELATED_DISCOVERY

TRENDING