openclaw - 💡(How to fix) Fix [Bug]: plugins install ignores --dangerously-force-unsafe-install (2026.4.2 d74a122) [2 comments, 3 participants]

Bug type

Regression (worked before, now fails)

Beta release blocker

No

Summary

openclaw plugins install still blocks installation on dangerous-code findings even when --dangerously-force-unsafe-install is provided. Plugin Github: https://github.com/albertbuchard/forge

Environment

• OpenClaw: 2026.4.2 (d74a122)
• OS: macOS (path is /Users/...)

Steps to reproduce

openclaw plugins install --dangerously-force-unsafe-install forge-openclaw-plugin

Expected behavior

Install proceeds (break-glass override accepted), or at least the flag affects scanner blocking as documented.

Actual behavior

Install is blocked with dangerous scanner findings:

• Shell command execution detected (child_process) in:
• scripts/build.mjs:19
• dist/openclaw/local-runtime.js:207
• Environment variable access combined with network send in:
• dist/server/services/calendar-runtime.js:40
• dist/openclaw/local-runtime.js:209

Then fallback text appears: Also not a valid hook pack: Error: package.json missing openclaw.hooks

OpenClaw version

2026.4.2 (d74a122)

Operating system

MacOS 26.3.1

Install method

install-cli.sh

Model

gpt-5.4-mini

Provider / routing chain

openai-codex

Additional provider/model setup details

No response

Logs, screenshots, and evidence

## Full CLI output
Plugin "forge-openclaw-plugin" installation blocked: dangerous code patterns detected: Shell command execution detected (child_process) (/Users/omarclaw/Documents/aurel-monorepo/projects/forge/openclaw-plugin/scripts/build.mjs:19); Environment variable access combined with network send — possible credential harvesting (/Users/omarclaw/Documents/aurel-monorepo/projects/forge/openclaw-plugin/dist/server/services/calendar-runtime.js:40); Shell command execution detected (child_process) (/Users/omarclaw/Documents/aurel-monorepo/projects/forge/openclaw-plugin/dist/openclaw/local-runtime.js:207); Environment variable access combined with network send — possible credential harvesting (/Users/omarclaw/Documents/aurel-monorepo/projects/forge/openclaw-plugin/dist/openclaw/local-runtime.js:209)
Also not a valid hook pack: Error: package.json missing openclaw.hooks

Impact and severity

Affected users/systems/channels Users on OpenClaw 2026.4.2 (d74a122) attempting to install forge-openclaw-plugin via: openclaw plugins install --dangerously-force-unsafe-install forge-openclaw-plugin openclaw plugins install --dangerously-force-unsafe-install -l <local-path> Affected system observed: local CLI/plugin install flow (not channel-specific runtime messaging flow).

Severity Blocks workflow for this plugin’s standard install path (high for plugin adoption/onboarding). No observed evidence of direct data loss or message loss from this issue itself.

Frequency Always in observed repro (reproduced with both npm-spec install and local linked install in provided logs). Broader population frequency beyond this repro: NOT_ENOUGH_INFO.

Consequence Plugin installation fails despite break-glass flag. Users are forced to use plugins.load.paths as workaround (worse install UX/manual setup). Practical impact: onboarding friction and significant wasted maintainer time (explicitly reported).

Additional information

This plugin legitimately:

• starts/manages a local Forge runtime
• reads local config/env
• talks to local Forge API

plugins.load.paths still works, but plugins install path is blocked even with the unsafe override.